View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820675#3820675
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820675 Thinking about it a little further, even the TX interceptor case state is only meaningful for the lifetime of that invocation. Keeping the state around in memory of the server when there is no ongoing invocation seems a little wasteful. Stateful implementations are easier to implement than stateless though. However, people have managed to build easy to use APIs on top of stateless HTTP invocations that hides the complexity from the developer so why could we not do the same? ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
