Re: Using pageWithName method problem
Re: Using pageWithName method problem
- Subject: Re: Using pageWithName method problem
- From: Art Isbell <email@hidden>
- Date: Wed, 21 Jul 2004 12:47:13 -1000
On Jul 21, 2004, at 12:08 PM, Kranthi Sagar Borra wrote:
1. Is there any difference between setting the current page component
in the next page, so that the user can access the previous page and
setting the current page component in the session variable , so once
the user goes to the second page and when he wants to come back to the
previous page, he can access the session variable. But soon after he
access this variable, he will set the session object to null so that
it is not carried forward.
A general rule is to minimize Session size as much as possible. After
each request-response cycle, the Session is stored. The more Session
instance variables (state), the more time and memory are required to
store and restore the Session.
If you're passing an object from one component to another, there's no
reason to add another Session instance variable to store this object.
If multiple components need to access an object, then the Session might
be the best place to store it.
Aloha,
Art
_______________________________________________
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.