Hi Jiang,
see this link
http://code.google.com/appengine/docs/webapp/requesthandlerclass.html
get()
post()
put()
head()
delete()
On Aug 27, 10:22 am, Jiang <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a quick question: does app engine support form "PUT" and
> "DELETE"?
>
> They are covered in on
Hi Davide,
Thanks for your reply but i still get the problem. For example, i have
a simple class:
class SimpleService(RequestHandler):
def get(self):
self.response.headers['Content-Type'] = 'text/plain'
self.response.out.write('get')
def post(self):
self.response
How are you making the put and delete requests? Most ajax libraries
I've seen, fake out PUT and DELTE by sending a flag with the operation
name as a parameter to POST and rely on the webservice understanding
that. See:
http://dobrzanski.net/2007/04/22/using-put-and-delete-methods-in-ajax-requesta
see --> self.request.method
def get(self):
logging.info("" + self.request.method)
self.response.out.write('get')
def post(self):
logging.info("" + self.request.method)
self.response.out.write('post')
def put(self):
logging.info("" + self.request.met
> Put this as vote to provide multithreaded dev server. I promise I
> won't start my own hosting farm.
A multi-threaded dev server only makes sense for thread-safe
applications.
Currently the app engine platform doesn't expose anything that can be
used to make thread-safe applications. Since th
Surely, the WSGI request handler itself is thread safe, not? I assume
that the deployment environment is running a threaded interpreter. I
would be suprised if App Engine is running an interpreter-per-request
setup.
The api does not block me from using RLock from the threading
module... is there
It isn't enough that the request handler and other library/platform
code be thread safe, the application must be as well.
> Because I'm
> assuming that in
> production the same interpreter may be handling many WSGI threads and
> thi
