Comments on: More Reasons to Avoid State http://www.subbu.org/blog/2004/12/more-reasons-to-avoid-state HTTP, REST and some Cycling Wed, 07 Jan 2009 12:18:28 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Subbu Allamaraju http://www.subbu.org/blog/2004/12/more-reasons-to-avoid-state/comment-page-1#comment-13 Subbu Allamaraju Mon, 27 Dec 2004 16:21:29 +0000 http://wp.subbu.org/2004/12/more-reasons-to-avoid-state/#comment-13 <p>Regarding the comment "You're mixing things up: statelesness/statefulness does not have anything J2EE deplyment descriptors..."</p> <p>True. The issue is not about deployment descriptors, but the way most of these servers maintain their own state. The result is rigidity.</p> Regarding the comment “You’re mixing things up: statelesness/statefulness does not have anything J2EE deplyment descriptors…”

True. The issue is not about deployment descriptors, but the way most of these servers maintain their own state. The result is rigidity.

]]> By: No one http://www.subbu.org/blog/2004/12/more-reasons-to-avoid-state/comment-page-1#comment-12 No one Mon, 27 Dec 2004 13:54:53 +0000 http://wp.subbu.org/2004/12/more-reasons-to-avoid-state/#comment-12 Try to build any application without state. It's impossible. Try to build any application without state. It’s impossible.

]]> By: Behrang Saeedzadeh http://www.subbu.org/blog/2004/12/more-reasons-to-avoid-state/comment-page-1#comment-11 Behrang Saeedzadeh Mon, 27 Dec 2004 13:39:17 +0000 http://wp.subbu.org/2004/12/more-reasons-to-avoid-state/#comment-11 You're mixing things up: statelesness/statefulness does not have anything to do with J2EE deplyment descriptors. Deployment descriptors are necessary, whether you want to maintain state in your application or not. And the problem with shopping cart config file can be solved without losing state. One way can be to check the modification date of the config file periodically. And this also is not only a problem that stateful applications: A stateless application may also load some configuration parameters from config files at deployment time. By the way, you're talking about session state, aren't you? And I'm not sure if it's good to avoid state or not, but whatever, happy new year ;-) You’re mixing things up: statelesness/statefulness does not have anything to do with J2EE deplyment descriptors. Deployment descriptors are necessary, whether you want to maintain state in your application or not.

And the problem with shopping cart config file can be solved without losing state. One way can be to check the modification date of the config file periodically. And this also is not only a problem that stateful applications: A stateless application may also load some configuration parameters from config files at deployment time.

By the way, you’re talking about session state, aren’t you?

And I’m not sure if it’s good to avoid state or not, but whatever, happy new year ;-)

]]> By: John D. Mitchell http://www.subbu.org/blog/2004/12/more-reasons-to-avoid-state/comment-page-1#comment-10 John D. Mitchell Mon, 27 Dec 2004 12:40:36 +0000 http://wp.subbu.org/2004/12/more-reasons-to-avoid-state/#comment-10 "State is the second worst thing in distributed computing.<br />  No state is the worst." --John Ousterhout “State is the second worst thing in distributed computing.
 No state is the worst.” –John Ousterhout

]]>