md wrote:
My question is with regards to whether I need or
should put the submitted data into the session as the
user navigates the forms (to create an account). The
user will be taken through three forms to create an
account. So for instance, form one will ask the user
to create a username,
On Mon, 9 Dec 2002, Perrin Harkins wrote:
md wrote:
My question is with regards to whether I need or
should put the submitted data into the session as the
user navigates the forms (to create an account). The
user will be taken through three forms to create an
account. So for instance,
Rafiq Ismail (ADMIN) wrote:
I'm not sure how often a user will attempt to complete one form through
multiple browsers. To be honest I'm not sure that he/she should.
There are all kind of forms. An obvious example would be a search.
Users often open up multiple windows when browsing a site
--- Perrin Harkins [EMAIL PROTECTED] wrote:
Todd W wrote:
I have a table with some basic user information
(first name, last name,
address,
phone number, etc...).
That's permanent data, not session data. Session
data is transient.
I was reading through the archives and came across
It's just a storage mechanism. Typically the procedure is that one a user
identified herself with some kind of login process, you put her user ID (a
primary key to a database table) into the session, and keep it as a key for
accessing that data.
I have a table with some basic user
Todd W wrote:
Im looking at Apache::Session and trying to figure out what it does.
It provides shared storage of a hash of data, and gives you a unique ID
that you can tie to a user.
From what I
can tell, Apache::Session will only give generic sessions, of which I know
nothing about the
Im looking at Apache::Session and trying to figure out what it does. What I
want
to do is tie sessions to a particular record in a database table. From what
I
can tell, Apache::Session will only give generic sessions, of which I know
nothing about the user untill they give me information
