Skip to content

Adjust public APIS for ENGINE removal #1337

@nhorman

Description

@nhorman

Removal of engines means we have numerous APIs which will have an ENGINE parameter that is no longer used.

We need to determine a method for which this parameter is handled or eliminated

My current proposal is:

  1. Public API functions which are deprecated should not be modified. For those the api should be left alone, including the ENGINE parameter. Use of the ENGINE parameter becomes vestigual and is documented as not being used, and that passing any value other than NULL will result in an error.

  2. Functions which are not deprecated can have their ENGINE parameter removed entirely and docs updated accordingly. Given that this is being done on a major release boundary, API alterations should be allowed for this

  3. The canonical ENGINE apis (ENGINE_init/get_id/etc), should be eliminated entirely

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions