in reply to State-keeping modules

I have not used CGI::Session or Apache::Session, but I have written a fairly simple module for maintaining state without cookies.

What I do is create a unique ID string, parse the html before it's outputted and tack it on to the end of any link. All ID's are tracked from a Mysql database, but they needn't be and could be kept in temp files.

That is a simplified explanation of what my module actually does, but as the implementation of stateful sessions over http seemed fairly straight forward I didn't even think to see if there was a module pre-written for it.

Replies are listed 'Best First'.
Re^2: State-keeping modules
by BUU (Prior) on Mar 02, 2005 at 21:13 UTC
    Sure, that's not a bad idea, but what happens when someone book marks the link? What about somebody copying the url and passing it to a friend? What about storing the link in an online bookmark type site? What about pasting it to a forum or something to share it?
      I use CGI::Session to maintain state in my applications. I also tack the CGISESSID value onto the end of each url in case a user does not have cookies enabled.

      I understand your comment on bookmarking and linking problems with session-id-appended urls, but am not sure if there are any other ways to deal with browsers with cookies turned off, or user agents with no cookie capability. Any suggestions? (I'm open to other options from what I am using at the moment for those reasons outlined)