[Seaside-dev] Issue 287 in seaside: encoding code

[codesite-noreply at google.com]

Comment #5 on issue 287 by renggli: encoding code
http://code.google.com/p/seaside/issues/detail?id=287

I am thinking of introducing a WAResponseStream that does encode all output  
on the fly, instead of doing that
separately in all the server adaptors. By default a WAResponseStream is  
binary, this means it does not do any
encoding. Presumably the WARenderContinuation will set the encoding as set  
in the application, this happens
where the content type of the response is set too. This has the advantage  
that the encoding is decoupled from
the server adaptors, which is kind of ugly right now. Does that make sense?  
How does that integrate with the
above changes?


--
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