On Wed, Jun 10, 2009 at 21:12, Dmitry<[email protected]> wrote: > Hello, > > Sorry if I'm missing a point, but why not use XOP for the URLs > > I mean that it's a standard way to use it as a binary optimizations in > SOAP, but not necessary in way SOAP does it... > > <some_object> > <xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include"; > href="http://some_site/big_file.bin"/> > </some_object>
That does sound like a very good option if it's not too hard to create server side. Not sure if it really would be much worth it if the server is actually still putting the data there in the MIME attachments - that would still go over the wire - you would only remove the problem of having a massive base64-encoded thing mess up for the XML parsers - in addition to that the client could put it straight to disk and not waste as much memory. Do you know if MIME attachments would be the case with your example code - or would you get a 'real' URL that you can retrieve the data from afterwards - if you need it? And that you can pass up again as a parameter? -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ taverna-hackers mailing list [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/taverna-mailing-lists/ Developers Guide: http://www.mygrid.org.uk/tools/developer-information
