a) We have an app with an applet interface. At periodic intervals the applet goes to server and gets updated data and repaints. On the server side now, there is a stateful session bean that holds the object data painted by applet. Whenever there is a change to the data of objects held by stateful bean, then the object referrred to by stateful session bean is updated. Can I reap a lot of benefits if I move from stateful to JBoss cache(generally speaking)
b) The above described is an existing system...and I want to suggest JBoss cache to client (in lieu of stateful session beans)and hence was looking for an article or write-up that compares stateful and JBoss cache...is there one? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955105#3955105 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3955105 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 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
