Re: Sessionless Direct Actions
Re: Sessionless Direct Actions
- Subject: Re: Sessionless Direct Actions
- From: Pierre Frisch <email@hidden>
- Date: Sat, 31 May 2003 11:26:53 -0700
I disagree with you. Lets take the example of a catalog the user looks
at item in a category. It is beneficial to keep the item and the
category he is looking at between two request as most often he will ask
for a related object or another one in the same category. Not having to
refetch the object is a nice performance enhancement. Using the session
to do this is convenient and all the mechanism are already there.
What you are doing with the ContentContext is different you are
building a system wide object cache which may of may not work on a
specific application depending on what you are doing. It also depends
on the rest of project wonder where I was only pointing to a design
pattern.
Pierre
On Saturday, May 31, 2003, at 10:10 AM, Jonathan 'Wolf' Rentzsch wrote:
Pierre Frisch, email@hidden, wrote:
I would like to add just one thing. Sessions are not bad in themselves
and can bring quite a bit of speed improvement to a DirectAction
application by caching the objects
Caching which objects? Consider a stateless WOComponent. Does it get
cached in a way when using sessions than when you don't?
an cutting the number of fetches you
need at each request.
My ContentContext allows fetch spec caching sans sessions:
<http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/wonder/Wonder/
Experimental/
WOWebLog/ContentContext/>
_______________________________________________
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.