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.
Alexander. On Thu, Apr 19, 2012 at 5:05 PM, Burak Arslan <[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] > http://mail.python.org/**mailman/listinfo/soap<http://mail.python.org/mailman/listinfo/soap> >
_______________________________________________ Soap mailing list [email protected] http://mail.python.org/mailman/listinfo/soap
