Date: 06/29/99
- Next message: jim: "[PHP-DEV] CVS update: php3/win32"
- Previous message: Rasmus Lerdorf: "RE: [PHP-DEV] overloading JNI return values"
- In reply to: Rasmus Lerdorf: "RE: [PHP-DEV] overloading JNI return values"
- Next in thread: Rasmus Lerdorf: "Re: [PHP-DEV] overloading JNI return values"
- Reply: Rasmus Lerdorf: "Re: [PHP-DEV] overloading JNI return values"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Quoting Rasmus Lerdorf <rasmus <email protected>>:
> I haven't looked at that part of the code, but David Sklar's idea about
> using the mod_jserv protocol to talk to a persistent JVM seems like a good
> place to start to me.
I'm curious... this happened, and a persistant JVM was used, would this mean
that we'd suddenly have a persistant resource accessible from any httpd
process that would store objects that didn't need to be
serialized()/unserialized() at every script invocation? I know it would only
be for people using the JVM, and I don't know about memory usage, but it
seems that could be huge win for people with complex session information to
store...
-chuck
-- Charles Hagenbuch, <chagenbu <email protected>> -- "sleep comes from acorns." - jess-- PHP Development Mailing List (http://www.php.net/) To unsubscribe, e-mail: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: jim: "[PHP-DEV] CVS update: php3/win32"
- Previous message: Rasmus Lerdorf: "RE: [PHP-DEV] overloading JNI return values"
- In reply to: Rasmus Lerdorf: "RE: [PHP-DEV] overloading JNI return values"
- Next in thread: Rasmus Lerdorf: "Re: [PHP-DEV] overloading JNI return values"
- Reply: Rasmus Lerdorf: "Re: [PHP-DEV] overloading JNI return values"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

