On May 12, 11:56 pm, Toby Reyelts <[email protected]> wrote: > arjan, > > There are two sides to the App Engine API: the client and the server. The > client side (appengine-api.jar) lives entirely in "user-land". If you so > chose, you could create your own version of these classes. > ...
But that's the case the other way too. For example spring-test implements parts of the servlet-api as stubs for testing reasons. That's not affected at all by which classloader servlet-api is provided at runtime. > Having this separation means that you can evolve the client and server > independently. For example, dev_appserver and prod obviously have two > different server backends for the same client API. You can take that one > step further and even independently implement your own server if you so > chose. It also means that its trivial to do things like test out and even > deploy hotfixes for individual applications instead of waiting for full > releases. I don't see how you can evolve and API is affected by which classloader provides it. Cheers Philippe -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
