You should be able to make your pic talk to another system using SOAP.  SOAP /is/, as you said, just XML over HTTP - you can hard-code the headers and concatenate your data.

The big question is:  Is someone going to send SOAP requests to you (the pic)  - or are you sending them to someone else.  That is, who is the 'server' and who is the 'client'?


-matt redmond

>
> From: William Couture <bcouture@CRIS.COM>
> Date: 2004/08/23 Mon PM 03:58:15 GMT
> To: PICLIST@MITVMA.MIT.EDU
> Subject: [OT:]  Anyone know anything about the SOAP protocol?
>
> Hi!
>
> I'm hoping someone here knows anything about the SOAP
> protocol.
>
> For a project at work, someone is asking if our product can
> do SOAP. Of course, I look around to find it's HTTP/XML,
> and so (despite it's name of Simple Object Access Protocol),
> it's not all that simple and not the sort of thing you can
> easily setup on a tiny embedded processor (18F252 that's
> already running the rest of the system if you're wondering).
>
> Nonetheless, try explaining this to managers...
>
> So, does anyone know SOAP well enough to know if I can pull
> a "trick" like precomputed headers/trails, so that our data
> can be embedded in a message by doing
>    {header}data{trailer}
> where header/trailer is all the HTTP/XML junk? Do any
> handshaking messages need to be exchanged, or can I just
> send messages out as needed?
>
> And, if I can do that, would there be a problem if the data
> is binary instead of ASCII?
>
> Thanks,
>    Bill
>
> --
> http://www.piclist.com hint: To leave the PICList
> mailto:piclist-unsubscribe-request@mitvma.mit.edu
>

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu