The old 3.0 user manuals explain that I believe, anyway as I understand it Properties can be persistent, which means that they will be tied to a session and be available across multiple requests by the same user. A property can be defined for page/component as us like in the specification.
The property isn't bound to the page but rather to the session. When a page is activated the persistent properties are tied to the page. Once the request has completed the tie is broken and the page is returned to a pool ready to be used by any session. To you as an application programmer though, it will appear as if there is a page object in memory, which remembers the persistent properties. Henrik "Cosmin Bucur" <[EMAIL PROTECTED]> skrev i en meddelelse news:[EMAIL PROTECTED] >I wanted to know if there's a pool of page objects which are used whenevevr >needed , or if , when a page object is accesed by a user , it gets >associated with that user's session on the server , therefore variables >stored by the user on a page would be available to the user later through >that same page ? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
