Date: 03/10/00
- Next message: Alexander Aulbach: "Re: [PHPLIB] Sessions slow?"
- Previous message: Roman Kalenjuk: "Re: [PHPLIB] Need idea on handling kill -9 signal"
- In reply to: Lukasz Kowalczyk: "[PHPLIB] builtin serialize() vs. Session->serialize()"
- Next in thread: Kristian Koehntopp: "Re: [PHPLIB] builtin serialize() vs. Session->serialize()"
- Reply: Kristian Koehntopp: "Re: [PHPLIB] builtin serialize() vs. Session->serialize()"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, 9 Mar 2000, Lukasz Kowalczyk wrote:
}Why does the Session class define its own serialize() function while
}there's a builtin having the same name and functionality? Is the Session's
}one better in any way?
This would be interesting to compare, perhaps someone who is willing to
use the serialize()-function of PHP inside PHPLIB?
But to answer the question: Now it isn't better any more. serialize() can
handle all types of variables. But Session has some more "cool" features,
which could be sometimes very important.
--SSilk - Alexander Aulbach - Herbipolis/Frankonia Minoris - (0931)22032
- PHP3 Base Library Mailing List. Send messages to <phplib <email protected>>. To unsubscribe, send "unsubscribe" to <phplib-request <email protected>> in the body, not the subject, of your message.
- Next message: Alexander Aulbach: "Re: [PHPLIB] Sessions slow?"
- Previous message: Roman Kalenjuk: "Re: [PHPLIB] Need idea on handling kill -9 signal"
- In reply to: Lukasz Kowalczyk: "[PHPLIB] builtin serialize() vs. Session->serialize()"
- Next in thread: Kristian Koehntopp: "Re: [PHPLIB] builtin serialize() vs. Session->serialize()"
- Reply: Kristian Koehntopp: "Re: [PHPLIB] builtin serialize() vs. Session->serialize()"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

