Hi Stephen,
What does ns_conn write_encoded false do (although it is somewhat self
explanatory)?
Also ns_startcontent is neat - saves me manually fudging the header
with ns_write.
On Fri, Aug 29, 2008 at 5:52 AM, Stephen Deasey [EMAIL PROTECTED] wrote:
On Thu, Aug 28, 2008 at 9:50 AM, Mark
Hi all,
If I Ns_Log() the data in a (char *) I can clearly see that it
contains newlines, and I can also verify that it contains nulls with
memchr.
I have tried any number of ways to turn it into a tcl object, eg:
objPtr = Tcl_NewByteArrayObj(str, length);
or
objPtr =
Mark,
Hard to say what you are actually trying to do, but UTF-8 is a byte
array, if you want to call it that. The problem you are seeing may be in
displaying what the bytes are (which might not work for binary data, try
cat'ing a binary file and watch the fireworks.)
tom jackson
On Thu,
On Thu, Aug 28, 2008 at 9:50 AM, Mark Aufflick
[EMAIL PROTECTED] wrote:
Hi all,
If I Ns_Log() the data in a (char *) I can clearly see that it
contains newlines, and I can also verify that it contains nulls with
memchr.
I have tried any number of ways to turn it into a tcl object, eg:
On Fri, Aug 29, 2008 at 3:18 AM, Mark Aufflick
[EMAIL PROTECTED] wrote:
Hi Stephen,
What does ns_conn write_encoded false do (although it is somewhat self
explanatory)?
With the write_encoded flag set (which ns_startcontent sets) ns_write
will assume you're sending character data and will