Hi, I haven't looked at WebWork before but wouldn't the best way to do this be to provide a proxy of the resource to the Action. Then if any mutating operation is called on proxy mark the object as dirty and then at the end of execute save it back into distributed session.
If the object is not proxy-able then you can serialize the object before execute then serialize it after execute. Then do a byte comparison on serialized form and only save it back to session if it has changed. Of course this would introduce a significant overhead and you may need to introduce a strategy layer in between to determine what you want to do. A similar strategy could be used for resources passed into Pico Components. ie Pass a proxy into ctor and then only save "dirty" data into session at the end of each request. ----- Original Message ----- From: "Jason Carreira" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> Sent: Tuesday, July 08, 2003 10:23 AM Subject: [picocontainer-dev] FW: [OS-webwork] webwork in a cluster > This is a very good question... I'm forwarding to the Picocontainer > list... Any ideas? > > -----Original Message----- > From: Morten Wilken [mailto:[EMAIL PROTECTED] > Sent: Sunday, July 06, 2003 5:57 AM > To: [EMAIL PROTECTED] > Subject: [OS-webwork] webwork in a cluster > > > I discussed this with Mik and Jason at TSS Symposium but i just wanted > to post it here so it doesn't get lost: > > I thinke there might be an issue with the IoC approach when using > Webwork in a cluster. As i understand it you can declaratively specify > that an object should live in the Session scope, and then have an Action > implement an *Aware interface so your Action gets the object from > session set > > The problem is that in a cluster (alteast on Orion and Weblogic) you > need to explicitly set the object back in the HTTPSession if it has > changed, because the servers need to know when you have changed an > object in order to notify other servers in the cluster (usually through > multicasting). > > The simple solution to this is to explicitly set the object back in the > HTTPSession after the execute() method is called. The overhead is > minimal and it will then work in a cluster. > > sincerely > morten wilken > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > _______________________________________________ > picocontainer-dev mailing list > [EMAIL PROTECTED] > http://lists.codehaus.org/mailman/listinfo/picocontainer-dev > > ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
