use different clock functions, which can cause timeouts to be delayed
(in some cases until the next fetch is started). This change
resynchronizes the schedule after each timeout call.
to be more consistent with our handling of query parameters.
This change is slightly backwards-incompatible: applications that have
already added an unquote() call on arguments to RequestHandler.get/post
will need to remove them.
This change replaces an earlier (reverted) commit:
7b80c2f4db
This reverts commit 7b80c2f4db.
URI spec requires that '/' and '%2F' be distinguishable, so it's incorrect
to escape at this level. The next commit will instead unquote captured
groups before passing them to get()/post() in web.py
consistent with our handling of query parameters (especially important
when capturing groups are used in the URLSpec regex).
This change is slightly backwards-incompatible: applications that have
already added an unquote() call on arguments to RequestHandler.get/post
or use percent escapes in URLSpec patterns will need to remove them.
instead of after running user callbacks, since those callbacks might have
started using file descriptors that were closed by curl in perform().
Thanks to David Novakovic for the fix. Adapted from
6df99e948e
By default we check that the method is one of the standard ones (and
is capitalized correctly), but this can be overridden to work with a
server that has implemented nonstandard methods (e.g. CouchDB)
http://github.com/facebook/tornado/issues/issue/90
This change was motivated by google app engine's xmpp support,
which uses different spacing in the header than other common clients
and quotes its boundary string.
Based on changes by jehiah:
18cb45ca739d67963466
This reverts commit 9ea5f8a277.
The one-shot behavior of receive_message was intentional, and simply
requeuing the old callback every time will eventually overflow the
stack due to repeated async_callback wrappers. An alternate interface
that doesn't require receive_message to be called for every message
may be added in a future change.
See discussion at
9ea5f8a277
Older versions of pycurl (including 7.16.2.1, which is the recommended
version for Mac OS X 10.5) only work with real functions, not objects
with a __call__ method like functools.partial.
Remove exception-swallowing - curl versions that predate HEADERFUNCTION
are no longer supported.
string. This is inconsistent with its write method, which encodes all
strings as ascii (and rejects unicode strings iff they have any
non-ascii characters). This change uses utf-8 as the default encoding
when constructing cStringIO objects in tornado.
Ben Darnell