Hello,
I find it extremely risky to do what you want to do: you don't know
where GAE (and its dev kit) is headed to ...
From the architecture perspective, you have 2 main dependencies
probably:
- servlet API
- datastore
You can fairly easily change for another container (tomcat for
Googlers have said many times that you should not use the dev server for
production. Among other things, It is single-threaded, so you don't get
concurrent request handling, and it is not hardened for security.
--
You received this message because you are subscribed to the Google Groups
Unless I'm mistaken, the Java dev_appserver is multi-threaded, but
everyone's given you good answers. Our first priority is making it a good
development experience.
On Tue, Mar 1, 2011 at 9:56 AM, Jay Young jayyoung9...@gmail.com wrote:
Googlers have said many times that you should not use the
Hi
Thanks for your guidance and giving me a better insight of java development
server.
@didier
Data store may not be an issue for us because we use mysql as we are using
RDBMS instance(Sql service) of Google app engine.
@Jay Young
If development server is single threaded, then it will
Rick, now that I think of it, the Java dev_appserver is based on Jetty,
which is multi-threaded. I was thinking of the python server (at least I'm
pretty sure I'd heard that). Toby was absolutely right.
--
You received this message because you are subscribed to the Google Groups
Google App
