well, I guess we could... I orginally steered away from that idea because it seemed that required the xml to be http encoded. Is that true? I also don't see why we would want the parameter, when it doesn't actually mean anything. The way we're doing it is closer to the way soap works. Whether that's good or bad - I don't know. This is also an external api, so we will be providing the server only. It seems more standard to me to just tell the client to post the xml as the request content instead of as a parameter value, but we're not locked into this.
I am posting xmls the same way you do - with httpclient. There are several advantages over sending xml as form field:
- smaller requests - with forms everything has to be encoded
- you may post bigger documents as you can read them on the server side from stream instead of parsing everything into a String.
-- Leszek Gawron MobileBox [EMAIL PROTECTED] http://www.mobilebox.pl
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
