On 8/14/06, Korbinian Bachl <[EMAIL PROTECTED]> wrote:
i think dirty() is quiet standard. it tells the object that you changed it and now it needs to do whatever it needs to do to react to that.
yes we could, but that would cause a ton of unnecessary replications and take away a lot of bandwidth inside the cluster.
-Igor
we like dirty() and havent had any complaints so far save this one. you can always do: MySession { public void sync() { dirty(); } } :)sure i can do this... i just meant u usually dont think about snycronising when seeing a "dirty()" - called function
i think dirty() is quiet standard. it tells the object that you changed it and now it needs to do whatever it needs to do to react to that.
aop sounds nice, if there was an intercepor for "change to any field value in any object in this instance" we might consider it. we are not aop wizs so maybe there is one and we dont know about it.im neither, but you could call it everytime a page is processed?
yes we could, but that would cause a ton of unnecessary replications and take away a lot of bandwidth inside the cluster.
-Igor
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
