[Seaside-dev] Issue 293 in seaside: Refactor WAResponse and subclasses to encapsulate stream and use WriteStream instead of ReadWriteStream

[codesite-noreply at google.com]

Updates:
	Status: Fixed
	Owner: WeybridgeWay

Comment #19 on issue 293 by WeybridgeWay: Refactor WAResponse and  
subclasses to encapsulate stream and use WriteStream instead of  
ReadWriteStream
http://code.google.com/p/seaside/issues/detail?id=293

I think that there was a tiny change in here somewhere, mostly dealing with  
Stream>>#'crlf'.

I still think that WAResponse is exposing more internals than is necessary,  
and insisting that it expose a Stream
protocol is excessive when the actual usage could be encapsulated with  
#'nextPutAll:' (and possibly #'nextPut:')
in the abstract superclass (at least as far as I've been able to tell).

--James

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings