[Seaside-dev] WAStreamedResponse vs WABufferedResponse

[Michael Lucas-Smith]

Lukas Renggli wrote:
>> When you're using the Comet stuff, how do you configure the server to use
>> the WAStreamedResponse. Do you start a second http server for the streamed
>> version or do you configure your main http server to use streaming instead
>> of buffering?
>>     
>
> In Seaside-Squeak there is a special server (WAListener) that uses
> WAStreamedResponse, the other servers (Kom, Swazoo) use the default
> WABufferedResponse as they lack support for streaming.
>
> Ideally the choice between WABufferedResponse and WAStreamedResponse
> should be a setting in the server adapter, similar to upload-streaming
> that is a setting in the Kom adapter. Most people probably want
> buffering during development, but streaming during deployment (as it
> is faster and less memory intensive).
>
> The choice has nothing to do with Comet, only that Comet requires a
> WAStreamedResponse. Currently Comet does not support to stream through
> a different server, but that could probably be added.
>
>   
It seems like it's favourable to leave it as a global switch between 
buffered and streaming for now then.

Thanks,
Michael