>--- Original Message ---
>From: Matt Redmond <mdredmond@CHARTER.NET>
>Date: 8/23/04 11:17:14 AM
>
>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'?

That's the real question, and one I'm trying to get more
information on from the applications engineer.

This is a RFID tag reader, and normally it operates in two
modes:  serial command or trigger command.

In serial command mode, when the reader gets a command, it
gets a message, does the action, and sends a reply.

In trigger command mode, actions are pre-determined, and
executed automatically when it receives a trigger signal.
The results are then sent.

>From the little I've been given, it *SOUNDS* like this would
be a trigger command application, which might be doable.  If
it were a serial comman application, I'd have to parse the
incoming XML stream, which I don't think is going to happen.

However, it's the HTTP transport that has me worried.  I
probably expressed it badly in my original message, calling
it "handshaking", but it's a matter of "push" versus "pull"
for content.

In normal HTTP (web browser), you as client start the data
request (contact a server to request a web page), and the
server sends the requested data.  ("push" spammers and their
pop-ups do not follow this model).

So, I'm worried about being the "server" in this model,
which means that I'll have to wait for the client to request
data, which means I have to parse incoming XML, and that's
probably beyond what I can do.

So, in SOAP, is it possible / permissable to "push" data as
I need, or do I have to wait for a request?

Thanks,
   Bill

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads