nsob is mostly used for text content. While the "copy" would work
with a binary file - a "get" would probably not work with a binary
file since it is set up over HTTP and the binary code might terminate
the HTTP response before intended. But that is just a guess. I have
not really read the RPC/HTTP code in nsdci.
M
On Oct 22, 2007, at 7:28 PM, Damien O'Rourke wrote:
Hi,
I've been experimenting with the components in nsdci, most
particularly the sob service, and am impressed with it. What I'm
struggling with though is if I store an image file to the sob with
nsob.copy and then try and retrieve it later with nsob.get, it only
returns the first 4 or 10 bytes of the file. If I do a nsob.put I
can then do a nsob.get successfully, but the image file stored by
the nsob.put command is not viewable with other image viewers. I
suspect this is an encoding/binary issue but haven't been able to
figure out the where and whyfor.
Any ideas on where the issue might be or whether it's even possible
to do what I want using the sob component?
Thanks
Damien O'Rourke
--
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.
