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

[codesite-noreply at google.com]

Comment #14 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'm a bit confused by comment #13. A couple minutes after I saved a fix,  
Julian suggested a better location and I
made the change. There should have been a very small window during which  
problems would occur. Further, if
things are loaded in the order specified by the LoadOrder wiki, then will  
things still be lost? Finally, my
understanding is that a primary purpose of 2.9 is portability, cleanup, and  
refactoring, and a great deal of
moving around is being done. Since we are still in alpha, I'm surprised by  
the direction to freeze packages.
--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