[Seaside-dev] Why does WABufferedResponse need a ReadWriteStream?

[Lukas Renggli]

> One alternative that I always liked a lot is to have a method
> converting a WriteStream to a ReadStream (without additional copies of
> the collection, so the memory cost is very low).  I added it to GNU
> Smalltalk so that I could pass equally well a WriteStream or a String
> to the compiler.  WAPlatform could add a #seasideReadStream method to
> WriteStream.
>
> Would this be feasible to implement in other dialects?  At worst you
> can do #on:from:to: but that's often unoptimized and will do a copy
> even when from=1.

I guess that should be easy. In the worst case you can always
implement it using "contents readStream". However such a conversion is
not needed at the moment :-)

Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch