Re: sessions causing refreshing not to work [message #178321 is a reply to message #178320] |
Sun, 03 June 2012 19:13 |
Denis McMahon
Messages: 634 Registered: September 2010
Karma:
|
Senior Member |
|
|
On Sun, 03 Jun 2012 16:43:07 +0200, Fred wrote:
> Le 03/06/2012 15:59, Michael Joel a écrit :
>> It is if the user wants to open to documents at once and tries to
>> refresh on.
>> I guess the easiest is to go with passing data by the url, not clean
>> looking but the information is the important thing.
> I see what you mean.
> It's not so bad. Many sites proceed like this with a permalink or a kind
> of request. And URL could be bookmarked to access to specific
> information.
Perhaps the issue here is using one web page to present too many
different sets of content? And it might be better to either separate the
required content by url.
If that's not possible, pass a "sub-session" (for want of a better term)
id in the get, and track in the session which sub-session was displaying
which set of content data. Sub-session ids would only be valid for the
current session, and could be fairly short, as you have a 62 element
alphabet to work with, 0-9A-Za-z, so eg 4 characters gives you 62^4 (over
14 million) identifiers.
You'd need to add a new sub-session id whenever you generated a link to
content that wasn't already in the session's table.
Rgds
Denis McMahon
|
|
|