This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Batching operations to avoid handshake overhead?

FormerMember
FormerMember

I see that there are currently BulkUpdate and BulkDelete methods, which allow one to change the same thing to the same thing on multiple objects, or delete multiple objects by URL.

Is it possible to batch up operations, and submit multiple disparate operations?  If I have a script that will be making large amounts of arbitrary object updates, it would make sense to batch them up to avoid the SSL handshake overhead that individual update operations experience, and then call a flush() operation to trigger ordered batch execution.

If it is not currently possible, can it be roadmapped?

  • We can look at that. Are you looking for transactional behavior (all these operations succeed or none of them happen at all) or stop-on-first-error or just run them all one by one and return a list of results?

  • FormerMember
    0 FormerMember in reply to tdanner

    Running them all and returning the results would be the most flexible, and place any atomicity questions in the hands of the interface library (IE, one could snapshot current state of objects to be altered, commit, and if any of the calls failed, compute the steps necessary to reverse the successful calls).  Implementing all 3 in SWIS and indicating the desired mode would be awesome as well.