Daniel Kulp wrote:
The last option would be to make the "Destination" stuff in http
plugable. The jetty stuff just provides a HttpDestinationProvider or
something into the http module. Jetty wouldn't subclass the http
factory or anything. It just provides functionality into the existing
http one.
Any thoughts?
This is sort of the problem I voiced with the split, that it didn't go
far enough, although especially for different implementations of
HTTPConduit.
I don't think you have to go as far as having a HTTPDestinationProvider.
I didn't understand the need to make a HTTPTransportFactory both a
Conduit Initiator and a Destination Factory. The ConduitInitiator and
Destination can be separate entities and "registered" as such, can't
they? or is that a namespace problem?
Cheers,
-Polar
