hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Make the getCapabitilies entry point optional

Browse Source 
The getCapabilities entry point is no longer required as long as all the
relevant capabilities are added to the static module parameters.
This commit is contained in:
Markus Mäkelä
2017-03-20 10:58:07 +02:00
parent 7bd05d4581
commit dd94374057
3 changed files with 21 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
include/maxscale/filter.h
View File

@ -51,7 +51,9 @@ typedef struct mxs_filter_session
/**
* @verbatim
* The "module object" structure for a filter module
* The "module object" structure for a filter module. All entry points
* marked with `(optional)` are optional entry points which can be set to NULL
* if no implementation is required.
*
* The entry points are:
* createInstance Called by the service to create a new instance of the filter
@ -61,10 +63,10 @@ typedef struct mxs_filter_session
* setDownstream Sets the downstream component of the filter pipline
* setUpstream Sets the upstream component of the filter pipline
* routeQuery Called on each query that requires routing
* clientReply Called for each reply packet
* clientReply Called for each reply packet (optional)
* diagnostics Called for diagnostic output
* getCapabilities Called to obtain the capabilities of the filter
* destroyInstance Called for destroying a filter instance
* getCapabilities Called to obtain the capabilities of the filter (optional)
* destroyInstance Called for destroying a filter instance (optional)
*
* @endverbatim
*
@ -97,7 +99,7 @@ typedef struct mxs_filter_object
* @c setDownstream and @c setUpstream functions.
*
* @param instance Filter instance
* @param session Client SESSION object
* @param session Client MXS_SESSION object
*
* @return New filter session or NULL on error
*/