I may be way off base with this one, and I don't mind people telling me I am if
that is indeed the case.
I have an XMLRPC client and server that supports various transactions. I'd
like to add the ability for the client to upload a file to the server.
In looking at the "extended types" that ws-xmlrpc supports, I noticed the
Serializable was there, and since a File is serializable, I thought I'd give
that a try. I got the transaction set up, but this appears to only transfer
the File object itself, and not the contents of the file, which is what I'm
interested in. I've been looking around but don't see any equivalently
Serializable implementing Object for the file contents.
I also thought of the possibility of pulling the contents of a file into a
large byte[] and sending that. This might work, but I could I potentially run
into encoding issues? And I'm also wondering if it even makes sense to try to
transfer a large amount of data via this mechanism. Would it be unreliable to
do so or prone to errors? Would the underlying HTTP transferring mechanism
chunk the large data up and send it in pieces?
Again, if I need straightened out here, please don't hesitate. In the end I'd
simply like to be able to have the client transfer a file to the server, and
I'm certainly open to suggestions.
Thanks,
Mike
