Re: How to avoid instantiation of new WOComponents when reloading?
Re: How to avoid instantiation of new WOComponents when reloading?
- Subject: Re: How to avoid instantiation of new WOComponents when reloading?
- From: King Chung Huang <email@hidden>
- Date: Tue, 06 Jan 2004 21:37:03 -0700
If you make your components stateless, then they will be shared between
all users, per thread (ie: globally if you don't have concurrent
request handling).
King Chung Huang
Learning Commons
University of Calgary
On Jan 6, 2004, at 3:39 AM, Andreas Kosmala wrote:
Hi All,
WO always creates all WOComponents newly when the User performs a
reload of a WO-app. The session seems not to change (since the
SessionId is in the submitted URL), so why are the components created
newly? Is it possible to avoid that, for I want to store some state in
the single components (for that's more structured than storing
everthing whithin the session) that should not get lost when
reloading?
thanks in advance
andreas
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.