Am Donnerstag, den 16.09.2010, 22:58 +0200 schrieb Armin Ronacher:
> - The async part.
> If I can't find someone that is willing to provide some input on that
> I will remove that section.
I see a problem here: The response tuple must be returned synchronously
according to web3. Once returned, the
On Sat, Sep 18, 2010 at 5:03 AM, Marcel Hellkamp wrote:
> With WSGI it was possible to yield empty strings as long as the
> application is waiting for data and call start_response once the headers
> are final. Not perfect, but at least non-blocking. Web3 removes this
> possibility. The headers mu
There's a framework called cogen and it relies on this policy.
-- ionel
On Sat, Sep 18, 2010 at 12:34, Ian Bicking wrote:
> On Sat, Sep 18, 2010 at 5:03 AM, Marcel Hellkamp wrote:
>
>> With WSGI it was possible to yield empty strings as long as the
>> application is waiting for data and call s
Marcel Hellkamp wrote:
> Am Donnerstag, den 16.09.2010, 22:58 +0200 schrieb Armin Ronacher:
> > - The async part.
> > If I can't find someone that is willing to provide some input on that
> > I will remove that section.
>
> I see a problem here: The response tuple must be returned synchronously
>
At 09:01 AM 9/18/2010 -0700, Robert Brewer wrote:
Marcel Hellkamp wrote:
>
> Removing any support for this type of asynchronism would render web3
> useless for all but completely synchronous and trivial applications.
> Even frameworks would have no way to work around this anymore.
I've run a few
