On 30 Jan 2006, at 09:13, Jules Gosnell wrote:
James Strachan wrote:
On 27 Jan 2006, at 18:54, Jules Gosnell wrote:
James Strachan wrote:
On 27 Jan 2006, at 18:20, Jules Gosnell wrote:
Dain,
David is talking about how SessionManagers (effectively
extended SessionFactories) should be plumbed into Geronimo
(i.e. GBeans), not about the API's describing Sessions
themselves.
I've looked at the stuff in modules/session - it looks very
similar to some WADI internals - there is loads of overlap
here. I have some serious plans for converging WADI with
ActiveSpace and would be happy to consider further changes to
reuse or contribute to your sessions module. We should talk.
I'll jot my ideas down and post them shortly.
How about just implementing the Session APi directly using WADI? :)
That's something that we could look at. I'd be interested to
hear you plans for actually integrating the sessions with some
container (web, ejb, etc...) as well - WADI is already doing this.
WADI is doing this for web only; the Session API is designed as a
client API to use for OpenEJB, Lingo, ServiceMix, Tuscany et al.
i.e. the containers would use the API directly.
err - wrong :-)
WADI already has various tier-independant abstractions and a
partial working OpenEJB integration )for SFSBs - Gianny Damour
Where does this live? Its news to me.
) and I am talking to Rajith Attapattu about Sessions for a number
of Web Service transports. So, I think we need to figure out how to
draw these two divergent threads together. I will look more closely
at your API and consider how WADI might implement them.
Long-term, I intend for WADI to converge closely with ActiveSpace.
Are you intending to use this Session API with AS ? or do you have
other plans ?
I'm not really considering distributed caching or POJO abstractions
to distributed programming in this thread; its a completely different
problem.
James
-------
http://radio.weblogs.com/0112098/