On 07/03/2008, Brian Smith <[EMAIL PROTECTED]> wrote:
> Graham Dumpleton wrote:
> > Anyway, WSGI 2.0 currently talks about returning a single
> > tuple containing status, headers and iterable. What if it
> > actually optionally allowed the response to itself be an
> > iterable, such that you could do:
> >
> > yield ('102 Processing', [], None)
> > ...
> > yield ('102 Processing', [], None)
> > ...
> > yield ('200 OK', [...], [...])
> >
> > I'll admit that I am not totally across what the HTTP 102
> > status code is meant to be used for and am sort of presuming
> > that this might make sense. Am sure though that Brian who
> > understands this sort of level better than me will set me straight.
>
> That idea doesn't really benefit Manlio's programs. Manlio's program is
> trying to say "use my thread for some other processing until some
> (external) event happens.
Okay, like some of our protocol discussions before, you possibly don't
see what I see in how what I suggested could be used. ;-)
Anyway, I am not the one battling for this, so will not try and
explain it further. Or I'll leave it to my sleep deprived hours in the
middle of the night. :-)
Graham
_______________________________________________
Web-SIG mailing list
Web-SIG@python.org
Web SIG: http://www.python.org/sigs/web-sig
Unsubscribe:
http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
