On Fri, 2006-07-21 at 17:04 +0100, David Illsley wrote: > > So why dont you set the required transport out into options , and you > > can do that as follows; > > option.setTransportOut(TransportOutDescription transportOut). > > These absolutely are the properties that matter and it is easy for > application to set them but I'm trying to allow the targeting to be > transparent to the application such that they can set the destination EPR > and the TargetResolver can realise that the service can be satisfied by > another URI and rewrite the target EPR transparently. This code could be > put in a handler which would work if the transport can't change but this > precludes a local-optimisation (as by this point the listeners for an > async invocation will already be set up for the http transport) and also > precluses the idea of different handler chains based on different > transports.
This can be done with a straight module .. I'm still not clear why we need to add a new programming model component for it. Why not just write a "router" module that does whatever function you want and inserts handlers before/after/wherever it wants? Synapse for example is capable of doing what you're looking for and it works simply as a module - there was no need to introduce anything new. Sanjiva. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
