Jeremy Boynes <[EMAIL PROTECTED]> wrote on 14/08/2005 02:44:40 AM:
> Aaron's recent thread on SSL has made we wonder if we should consider
> providing our own socket listeners for HTTP(S) and other protocols
> rather than using the ones supplied by the containers we are embedding.
>
> Reasons for doing it include:
> * ability to integrate with custom work managers (thread pools) and
> SSL infrastructure
> * consistency across all embedded containers
> * potential for multi-protocol support on one end-point
> (i.e. multiplexing everything over one port like WebLogic does which
> can make life easier when firewalls are involved)
> * potential for integrating with custom QoS frameworks e.g. allowing
> custom negotiation with load-balancers in a clustered environment
> * potential for hi-av version upgrades where we can version in a
> upgraded component and hand off the physical socket resulting in
> no loss of availability
>
> Note that none of those features are HTTP specific.
>
> The downside of course is that it may weaken integration between the
> listener and the container being embedded; for some containers they may
> be so closely coupled that doing this will actually make things
> difficult. For example, I think doing this would be fairly easy for
> Jetty, I don't know how easy it would be for Tomcat, OpenEJB, JMX,
> ActiveMQ etc.
This sounds like a good idea. I assume we aren't forcing containers to use this mechanism, so if someone want to integrate container X but doesn't initially want to go to this much effort, they can use X's socket listener and change to use Geronimo's in the future (although this migration will impact their configuration).
If we do end up going down this path, it would be worthwhile talking with the Derby project about SSL and authentication for the network server. AFAIK, this work hasn't been started yet, so it would probably be a good time to talk with them. See the mail thread from the links in http://issues.apache.org/jira/browse/GERONIMO-842 .
John
>
> --
> Jeremy
This e-mail message and any attachments may contain confidential, proprietary or non-public information. This information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this e-mail, please notify the sender immediately and destroy this e-mail. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this e-mail are those of the author personally.
- Re: Should we have our own socket listeners? sissonj
- Re: Should we have our own socket listeners? Dain Sundstrom
- Re: Should we have our own socket listeners? David Blevins
- Re: Should we have our own socket listeners? Hiram Chirino
- Re: Should we have our own socket listen... Jeff Genender
- Re: Should we have our own socket l... David Blevins
- Re: Should we have our own socket listen... James Strachan
- Thread Pool vs WorkManager Aaron Mulder
- Re: Thread Pool vs WorkManager Thomas P. Fuller
- Re: Thread Pool vs WorkMana... Dain Sundstrom
- Re: Thread Pool vs WorkMana... Aaron Mulder
