Marc,
I'm trying to gauge requirements for Jetty within a
JBoss-3 context.
This is what I have figured so far:
1. JettyService needs to be delivered as a self
contained SAR. So it can be hot-deployed onto a JBoss
node. My major concern here is whether the SAR is run
packed/unpacked. Unpacked is probably not much work.
Packed will probably require changes to Jetty itself
(need to investigate).
2. Clustered Session support - if an incoming http
request can be routed to any one of a number of nodes,
then HttpSession objects need to be transparently
distributed, in order that conversational state may be
maintained between client and webapp. I was thinking
that the simplest HttpSession implementation might be
a CMP Bean ? Is this how clustering is expected to
work in 3.0? Is this the sort of approach that you
would expect ?
Do you have any further primary issues that need
attention ? Once we have something working we can
address secondary issues such as tighter integration
with shared thread pools etc....
Jules
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
