Re: PHP 4.0 Bug #5152: Object passed in a session generateserrors when member functions are called
| From: | rasmus at lerdorf dot on dot ca | Date: | Thu, 22 Jun 2000 21:59:15 +0000 |
| Subject: | Re: PHP 4.0 Bug #5152: Object passed in a session generateserrors when member functions are called | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-22002@lists.php.net to get a copy of this message | ||
> On Thu, 22 Jun 2000, Rasmus Lerdorf wrote:
> > But since the class data is really not much use without the class
> > definition, I don't see the point in separating them. And it wouldn't be
> > that much additional data. It's not like this stuff is getting passes
> > back and forth across the wire. It's all local, so I don't see the size
> > as being any sort of issue. Although for the shared memory backend I
> > guess it is an issue.
>
> Yeah, but how would you serialize methods?
Perhaps serialize the opcodes? But that wasn't my main point. My main
point was simply keep a tie between the object data and the class
definition. What you serialize could just be a pointer to where to find
the class definition and then have the ability to autoload it.
-Rasmus