Frank Millman wrote:
Hi all
I have a question about wsgi.
As far as I can tell from the spec and from the reference implementation,
wsgi requires that each request from the client is responded to by one or
more headers, followed by the response body. It is then ready to handle
the next req
"Frank Millman" writes:
> So the question is, how can I achieve this with wsgi? If I detect that
> I have received a request out of sequence, I can queue the request,
> and send an empty response.
I don't see how that can help, on the server side. Even if you send the
responses in the right orde
On Wed, 2011-02-09 at 14:31 +0200, Frank Millman wrote:
> I am dabbling with writing an ajax-style app. On occasion, I want to send
> more than one message from the client to the server. It is important that
> the server processes the messages in the same order that they are generated.
> I have
Hi all
I have a question about wsgi.
As far as I can tell from the spec and from the reference implementation,
wsgi requires that each request from the client is responded to by one or
more headers, followed by the response body. It is then ready to handle the
next request.
99% of the time
