[MXS-402] Filter interface clientReply must match Router clientReply Created: 2015-10-09  Updated: 2017-12-01  Resolved: 2017-03-20

Status: Closed
Project: MariaDB MaxScale
Component/s: N/A
Affects Version/s: 1.2.1
Fix Version/s: N/A

Type: New Feature Priority: Major
Reporter: markus makela Assignee: Johan Wikman
Resolution: Won't Do Votes: 0
Labels: None

Issue Links:
Blocks
blocks MXS-848 Provide more info in qla log Closed

 Description   

There is no benefit from having different clienReply entry points for filters and routers. If the filter clientReply would also include the DCB where the reply came from, it would allow filters to be placed before and after routers. This would permit a sort of a "backend filter" which could modify the output of a router.



 Comments   
Comment by Johan Wikman [ 2017-03-20 ]

The API should get a bigger overhaul. This should be handled as part of that.

Generated at Thu Feb 08 03:59:01 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.