> You log in, you stream 1 or more requests, and you exit.
You missed the responses to the requests.
Is it:
A) connect/auth, request, request, request, response, response, response,
disconnect
-or-
B) connect/auth, request, response, request, response, request, response,
disconnect
(A) works fine over HTTP, (B) requires TCP. As mentioned,
SOAP supports either.
> If you want to set up a bulk registration interface, you can open a
> connection, stream all your requests, get all your answers back,
> and close the connection. You authenticate once, issue 100+
> requests, and exit. It is so much more efficient.
Bulk registration is in a single <OPS_envelope>, is it not? In that case
it is a *single* request with multiple actions, not mutiple requests.
Each <OPS_envelope> represents a request. Although there's no reason
why they couldn't be stacked and sent in a single stateless connection (A)
provided they are not dependent upon each other and you can distinguish
which answer response to which request.
Adam
