On 9/29/07, Vasiljevic Zoran <[EMAIL PROTECTED]> wrote: > > On 29.09.2007, at 12:22, Stephen Deasey wrote: > > > > > Does this make sense: > > It does make sense but it does not answer either > of my questions.
> How to handle binary streams > of unknown sizes i.e. how NOT to get Content-Length > included in headers by the server code? Then I guess that page doesn't make sense, because I thought it explained the situation :-) As far as I can tell, we already support streaming binary data, both to HTTP 1.0 and 1.1 clients (and also to non-HTTP custom clients). Can you show some example code? What did you expect would happen, what actually happened? > Still: what good is ns_startcontent when you have > ns_headers and ns_write? I don't think it makes sense any more. It came from the old ArsDigita encoding patches to aolserver-3.x. The idea was you would write your own headers using ns_write, then you'd call ns_startcontent to signify that you'd finished writing headers and were now going to write content in some particular encoding, so the ns_write command should now encode the data you pass it. Headers should always be ascii. Here's an example: http://naviserver.cvs.sourceforge.net/naviserver/naviserver/tests/tclresp.test?revision=1.14&view=markup#l_496 This is all handled automatically now, and ns_startcontent should not be used. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
