IMHO, using HA SFSB is the best solution. You'll have much less code that
implements the HA HTTPSession. Smaller code is always easier to understand
and maintain. Plus, getting all this stuff (HA SFSB HTTPSession) could be
implemented quicker.
Using an EntityBean is also an alternative, but my instincts tell me it will
not scale as well(if at all).
Regards,
Bill
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Sacha
> Labourey
> Sent: Monday, September 24, 2001 11:42 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] Re: [jetty-discuss] Re: Persistant HttpSession
>
>
> > |On my side, I have thought to it (even made some basic designs).
> > |Nevertheless, I will first work on the HA framework with Bill,
> > |SLSB, ... the
> > |HTTPSession trick is about in the same todo line as the SFSB
> (guess why).
> >
> > because the persistent cache is a SFSB...
> >
> > do I win?
>
> Well, I don't know... just an old indian trick to make other
> people's brain
> work for me ;)
>
> In fact, I think of two solutions:
> - either relying on SFSB for the HTTPSession thing, or
> - using the same HA services for HTTPSession and SFSB but making the
> HTTPSession work through EB and use these new HA Services to build a
> In-memory storage for EB
>
> For some irrational reason, I am currently more sensible to the second
> options... don't know why... (not an old indian trick this time)
>
> Cheers,
>
>
> SacHA ;)
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
