You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hivemind.apache.org by hi...@jakarta.apache.org on 2004/10/01 09:14:09 UTC
[Jakarta HiveMind Wiki] New: PartialPipelineFilterProposal
Date: 2004-10-01T00:14:09
Editor: AlbertKwong <ma...@yahoo.com>
Wiki: Jakarta HiveMind Wiki
Page: PartialPipelineFilterProposal
URL: http://wiki.apache.org/jakarta-hivemind/PartialPipelineFilterProposal
no comment
New Page:
AlbertKwong:
Currently a filter has to support all methods defined by the service to be pipelined. In some situations this is not desirable because
1. The service designer wants to allow only a subset of the methods to be filtered.
2. To optimize the performance of some methods.
Without support from the PipelineFactory, a designer can achieve the same objective by breaking down the interface into smaller interfaces, create a pipeline for one of these sub-interface only, and then build a facade to combine the small interfaces. However, this increases the complexity of the design.
A proposal solution is to modify the PipelineFactory so that the first Bridge short-circuits to the terminator if the caller calls a method that is not supported by filters. The factory shall be able to find these methods by comparing the filter interface to the service interface.
Calling sequence for a normal pipeline method:
''Caller -> Bridge1 -> Filter1 -> Bridge2 -> Filter2 -> Bridge3 -> Filter3 -> Terminator''
Calling sequence for a short-circuit pipeline method:
''Caller -> Bridge1 -> Terminator''
----
---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-cvs-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-cvs-help@jakarta.apache.org