[rareddy]

camdk3: If you can share your experiences for this feature or consider contributing it would be great help.

Thank you.

[camdk3]

I dont think I have enough experience to contribute. however...

The way it works is quite simple in essence - you simply save up an array of your salesforce objects, up to the batch limit of 200, and then when you call either update/upsert/insert you then send the whole array of 200 sobjects.

There's an example on the salesforce wiki!

What was hard for me in my structure - may not be such a problem for teiid - is working out when to send the array, and indeed returning the results such that the parent programe gets the results tied back to the correct records.

One thing worth noting, is that the batch of 200 is not like a database transaction which either works or doesnt - it's simply a bunch of 200 independant updates - and the reason it's faster is reduced network connectivity. So tying in that conceptual difference to apps that expect it to behave like a transaction can be tricky!

I presume the batching that salesforce implement is relatively standard, so it could apply to other web services too? ( I dont have much experience with other services at this time )

Hope that helps,
Dan

[jdoyle]

Thanks Dan.