On 20 September 2010 16:19, Robert Brewer wrote:
> > On Sun, 2010-09-19 at 21:52 -0400, Chris McDonough wrote:
> >
> > > I'm -0 on the server trying to guess the Content-Length header. It
> > just
> > > doesn't seem like much of a burden to place on an application and
> > it's
> > > easier to sp
Iwan Vosloo wrote:
> On Fri, 2008-07-04 at 13:39 +0100, Matt Goodall wrote:
>> Iwan Vosloo wrote:
>> You're correct that Twisted Web does not allocate a thread per request.
>> All requests are handled by an event loop in the main thread.
>
>> In Twisted, the
ting better.
>
> I attach some code to illustrate - and would appreciate some feedback on
> the idea and its implementation.
>
> -i
>
>
>
>
> ___
> Web-SIG mailing list
> Web-SIG@python.org
&
Hi,
One thing I keep meaning to mention, prompted by the possibility of
simplejson being sucked into the std lib, is the handling of JSON object
names.
"An object structure is represented as a pair of curly brackets
surrounding zero or more name/value pairs (or members). ***A name is
a
ere
there is a server-side Python object "bound" to a client-side JavaScript
object that manages a fragment of the page.
The Python and JavaScript Athena widgets can send messages when
necessary and at whatever granularity is applicable to the application.
- Matt
--
__
citly make use
of this from application code (i.e. sending images in "real-time" as GIF
frames).
Buffering to avoid sending any headers out of sequence is something the
templating engine or (perhaps) the web framework should do. The web
server should stick to shuffling bytes around the in
