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/03 15:15:31 UTC
[Jakarta HiveMind Wiki] Updated: PartialPipelineFilterProposal
Date: 2004-10-03T06:15:31
Editor: AlbertKwong <ma...@yahoo.com>
Wiki: Jakarta HiveMind Wiki
Page: PartialPipelineFilterProposal
URL: http://wiki.apache.org/jakarta-hivemind/PartialPipelineFilterProposal
no comment
Change Log:
------------------------------------------------------------------------------
@@ -1,4 +1,4 @@
-AlbertKwong:
+= Problem Description =
Currently a filter has to support all methods defined by the service to be pipelined. In some situations this is not desirable because
@@ -7,6 +7,8 @@
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.
+= Proposed Solution =
+
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:
@@ -17,4 +19,4 @@
''Caller -> Bridge1 -> Terminator''
-----
+= Discussions =
---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-cvs-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-cvs-help@jakarta.apache.org