SOAP: purpose of Customer_Action = null

[Wolfgang Orth]

Hello Bruce and all,

the Customer_Action of a Webservice knows several options:
* get
* insert
* update
* delete
* null

Question 1:
My intention is to send a Queue from the Client to the Server for further processing. In this case its not any insert etc of any single record. The queue holds many records, which then the server will integrate into a table. I don't want to issue a .POST() with 'Customer_Action = insert' 500  times.

So in this Customer_Action = null is the option to choose - right?

Question 2:
Are these option defined in any official protocoll or would it be legit to have our own additional options, to trigger special activities in the NetWebServiceMethod?
In this case I have nothing specific in mind. First of all I want to understand, where get / insert / update / delete come from.
Maybe one could send something like Customer_Action = alert, instead of null in some cases?
Or is it recommended to use null, having the "reason" of this 'alert' in a variable inside the xml?


Thanks,
Wolfgang

[Bruce]

>>  I don't want to issue a .POST() with 'Customer_Action = insert' 500  times.

I don't think you need to. If you set the action to Insert, and the request contains multiple records, then multiple records are added.

>> Are these option defined in any official protocol

no.

>> would it be legit to have our own additional options

yes.

cheers
Bruce