Apr 9 at 2:49pm, Jason Giangrande wrote:
> Kelly Hallman wrote:
> > Try it without serializing, it works.
>
> After retesting, it seems you are correct. I guess the same bad
> __sleep() code that was causing the object not to unserialize at all was
> also preventing automatic serialization.
Fo
Kelly Hallman wrote:
Apr 9 at 11:12am, Jason Giangrande wrote:
You shouldn't serialize() objects prior to assign to a session variable.
The default session handler automatically serializes the data. Assigning a
serialized object value to a session just adds redundancy and overhead.
Actually, on
Apr 9 at 11:12am, Jason Giangrande wrote:
> > You shouldn't serialize() objects prior to assign to a session variable.
> > The default session handler automatically serializes the data. Assigning a
> > serialized object value to a session just adds redundancy and overhead.
>
> Actually, only if
Kelly Hallman wrote:
Apr 9 at 1:44am, Jason Giangrande wrote:
Jason Giangrande wrote:
I'm having a problem unserializing objects that are passed from page to
page with sessions. Registered globals is disabled so I am using the
$_SESSION array to store session variable
When I var_dump() $_SESS
Apr 9 at 1:44am, Jason Giangrande wrote:
> Jason Giangrande wrote:
> > I'm having a problem unserializing objects that are passed from page to
> > page with sessions. Registered globals is disabled so I am using the
> > $_SESSION array to store session variable
> >
> > When I var_dump() $_SESSI
Jason Giangrande wrote:
I'm having a problem unserializing objects that are passed from page to
page with sessions. Registered globals is disabled so I am using the
$_SESSION array to store session variable and am not using
session_register(). Here's what I'm doing.
On first page:
$auth = ne
electroteque wrote:
May i ask what the advantage of storing objects in session is ? Does it
cause overhead ? Like should i store the most common classes like the db and
auth class in a session ?
The advantage of storing an object is to keep it's properties. This way
you can use values that have a
electroteque wrote:
May i ask what the advantage of storing objects in session is ? Does it
cause overhead ? Like should i store the most common classes like the db and
auth class in a session ?
No. A good time for storing an _object_ in the session is when the
object contains mostly data. Restori
: [EMAIL PROTECTED]
Subject: Re: [PHP] Serializing objects and storing them is sessions
Jason Wong wrote:
> On Friday 09 April 2004 11:07, Jason Giangrande wrote:
>
>>Jason Wong wrote:
>>
>>>What does the php error have to say about it?
>>
>>php error? I'm
Jason Wong wrote:
On Friday 09 April 2004 11:07, Jason Giangrande wrote:
Jason Wong wrote:
What does the php error have to say about it?
php error? I'm sorry but I don't know what you are talking about.
Sorry, I meant to say "php error log". You should ALWAYS enable full error
reporting. And
On Friday 09 April 2004 11:07, Jason Giangrande wrote:
> Jason Wong wrote:
> > What does the php error have to say about it?
>
> php error? I'm sorry but I don't know what you are talking about.
Sorry, I meant to say "php error log". You should ALWAYS enable full error
reporting. And whenever y
Jason Wong wrote:
What does the php error have to say about it?
php error? I'm sorry but I don't know what you are talking about. The
only error I get is that a call to a member function on a non-object.
Here's the error (path has been changed):
Fatal error: Call to a member function on a non-
On Friday 09 April 2004 02:10, Jason Giangrande wrote:
> When I var_dump() $_SESSION it appears to be a string representation of
> the object. However, when I try to unserialize() it and store it in
> $auth the value is bool(false) and not an object.
What does the php error have to say about it?
13 matches
Mail list logo
