Hi!
I'm referring to this entry in the ChangeLog:
* nsd/tclresp.c: Add the -binary switch to ns_headers to signify
that you
intend sending binary data (probably with ns_write) and that the
mime-type header should not have a charset declaration appended.
Eh? I cannot see that in the code. The current implementation
(as in CVS) simply decides this on existence of the last
(optional) paramater that would specify length of the response
to be included in Content-Length header.
As this is now implemented, I cannot create output headers that
have no Content-Length inside, although I would like to send
binary data AND I do not know how large that data would be
in advance.
I suggest either adding that option OR use the simple convention
of length=-1 that would specify binary datastream of unknown length.
Until we sort this out, I will just check-in the simpler (latter)
variant. If somebody objects I will rewrite it to "-binary" switch.
In conjuction to this, I would also like to know what is the purpose
of the "ns_startcontent" command? I cannot see that documented nor I
do understand how is this supposed to be used with ns_headers and
ns_write.
Cheers
Zoran
-------------------------------------------------------------------------
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
