That's what I believe as well. While ns_http is a different code base
- I think both suffer from the same binary termination issue. I'm not
sure if we saw this when using nsob with the old DCIRPC protocol -
but we never used it for binary, so when we moved to HTTP we probably
never thought it to be problematic.
Check out dcicommon/rpc.c and dcicommon/server.c (I think).
M
On Oct 22, 2007, at 9:08 PM, Jeff Rogers wrote:
Dossy Shiobara wrote:
What I'm struggling with though is if I store an image file to the
sob with sob.copy and then try and retrieve it later with nsob.get,
it only returns the first 4 or 10 bytes of the file.
SOB isn't encoding-aware and is actually really naive--it doesn't
handle
binary data well.
Not sure if this it related, but I was just looking at ns_http for
an unrelated purpose and it appears that it is not binary clean at
all, since it uses Tcl_SetVar which expects a null-terminated
string. Getting binary files typically resulted in a 4 byte
response, could be that an average jpg file has a null at byte 4.
-J
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the
Subject: field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
