No, we didn't have any troubles. But this might well be due to the fact, that we really don't care for session replication ;-). So we don't support transparent fail-over, which is not a problem for us since it's rarely needed (my experience). Anyway, I store a Hivemind-Service in the session and, as far as I know, Hivemind-Proxies just serialize as the service-id (stateless).
Marcus > -----Original Message----- > From: Henri Dupre [mailto:[EMAIL PROTECTED] > Sent: Friday, September 23, 2005 10:35 PM > To: Tapestry users > Subject: Re: Hibernate session model > > > On 9/23/05, Schulte Marcus <[EMAIL PROTECTED]> wrote: > > We're using using long sessions in two productive apps now. > It works great > > and, for us, simplifies development considerably. Our first > app using > > hibernate used Spring w/ session per request and it > generated some really > > nasty ad-hoc work-around-code. > > > > We've implemented the long-session Pattern as a Hivemind > service-model which > > was really easy to do. > > Did you have any troubles with sessions being serialized with a large > graph of objects? > Or did you find a workaround? > > Thanks, > > Henri. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
