Sessions use cookie unless you force the URL session ID. Once you do
that, your options are pretty limited. You must pass some sort of
identifier from page load to page load to track a session. This can
either be via cookie (a preferred method) or through GET or POST
variables. There is no other good way that I'm aware of.
Actually, you might be able to engineer a small persistant data store
based on a Flash object. I've seen this done before - I think there are
some javascript libraries that use this technique.
Why complicate things when you can just use cookies? I still don't
understand people's aversion to using them. They serve a very useful
purpose and the downsides are trivial.
-Micah
On 09/25/2007 01:51 AM, Chris Carter wrote:
Hi,
I have users loging in and posting jobs. Now once the data is posted to the
database, the next time the user logs-in he will be presented with two
pages.
1) Post more jobs
2) Visit this page and delete jobs that you posted.
If he choses to go to the page 2 and delete the jobs. The table that shows
up with his posted jobs actually is derived by capturing the email id he
used to enter while logging in. This email ID is maintained throughout the
session.
The session captures his login email id > checks for his data and shows up.
The question is: Is session the only and/or best way to achieve this
functionality. (Don't want cookies).
Is there some efficient session mechanism available to achieve this?
Thanks,
Chris
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
