[Seaside-dev] Issue 293 in seaside: Refactor WAResponse and
subclasses to
encapsulate stream and use WriteStream instead of ReadWriteStream
codesite-noreply at google.com
codesite-noreply at google.com
Fri Jan 23 02:24:06 UTC 2009
Comment #15 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
Lukas,
Since you undid essentially all of my refactoring of WAResponse, I was
wondering if you could give a bit more
detail on what I broke? I thought I had covered the the things you
mentioned (writing the header, rendering the
body, etc.), and I had all the tests running. Can you provide a walkback
showing what broke?
--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
More information about the seaside-dev
mailing list