On 04/19/2012 05:16 PM, Alexander Kolesnikov wrote:
To keep communication SOAP-like, you can use shared http resources.
1) To send big arguments, upload them to share with WebDAV, and
replace them by urls of created resources. These resources can be
placed on the same server where SOAP-server works.
2) To return big results, SOAP-server must publish them to this shared
storage and return their urls instead. Client can download them by HTTP.
Thanks for advice about using WebDAV!
Disadvantage of using separate server for storing files is that it
complicates remote calls: calling part should upload, then send request,
wait response and optionally remove uploaded files; called part receives
request, then downloads file, then sends response.
Since file uploading/downloading is done over HTTP I think better to
embed transferring file into GET/POST request, so that it will be
transmitted with request/response messages.
Alexander.
On Thu, Apr 19, 2012 at 5:05 PM, Burak Arslan
<[email protected] <mailto:[email protected]>> wrote:
On 19/04/12 15:55, Vladimir Rutsky wrote:
If I use plain HTTP in a REST-like way I need to manually
implement RPC functionality, like parse GET query arguments
and translate them into my function call, wrap files for
upload in POST request and so on. In both solutions (SOAP or
REST-like HTTP) actual data will be transferred over HTTP.
rpclib supports rpc via HTTP, have a look at the HttpRpc protocol.
The File object is supported and you can upload HUGE files using
the werkzeug's wsgi server and the file objects. I can put up a
sample code somewhere if you give me a few days.
best,
burak
_______________________________________________
Soap mailing list
[email protected] <mailto:[email protected]>
http://mail.python.org/mailman/listinfo/soap
--
Vladimir Rutsky
_______________________________________________
Soap mailing list
[email protected]
http://mail.python.org/mailman/listinfo/soap
