users@glassfish.java.net

Re: GlassFish V3 planning - What do *you* want in GlassFish V3?

From: <glassfish_at_javadesktop.org>
Date: Thu, 01 Nov 2007 17:19:41 PST

That'd be all well and good save that PHP and Java are completely different animals.

PHP doesn't have the lifecycle constraints the EJB components have. They also don't have the persistent class mechanisms that Java has (since you're running in a live heap). There is no protocol in Java to change the structure of an object on the fly, for example. But a dynamic loader needs to be able to support that kind of thing.

Of course PHP doesn't have that problem because everything is interpreted at request time and thrown away, there is no persistent state within the heap, no shared binary structures from request to request. Everything is made fresh on load.

What you want sound wonderful, but there are limitations imposed both via the spec itself, as well as the implementations that make this a Hard Problem. If it wasn't hard, we'd have it well solved by now.
[Message sent by forum member 'whartung' (whartung)]

http://forums.java.net/jive/thread.jspa?messageID=243397