Mark Rees wrote:
"André Medeiros" <andre.caum@xxxxxxxxx> wrote in message
news:1122558897.3590.11.camel@xxxxxxx
The point of sessions is that when you close your browser, you loose it.
I'm affraid that if you want sessions that last two weeks, you'll have
to make your own session handler :) but yeah, it's possible, and it
beats the crap out of the "fill form, store in db, fill form, store in
db" method.
Unless your user wishes to complete the form from a different machine, of
course.
I really don't understand the dogmatic antipathy to storing information in
the database. Sometimes it is a better solution - horses for courses.
Rolling your own session management tool, whilst undoubtedly fun and
satisfying, is hardly an appropriate solution to this type of enquiry, which
is apparently from someone taking their first steps in web development.
I should probably explain that I come from an ASP background and so have an
inherent mistrust of sessions, although I am coming to understand that PHP
sessions are much more reliable.
Sorry about the three posts before, my mistake.
No, I think I wasn't clear because of a fundamental misunderstanding on
my part of the problem of SESSIONS not lasting between ... uh...
sessions. In fact I think my very first post on the subject did in fact
say I wanted to store the answers on the db throughout the process, but
I got so excited at the prospect of having sessions store things that I
got distracted.
Anyway, thanks again to all who replied and for all the help I generally
receive here on the list!!
JJ
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
