Client side transactions

[bcamac]

Is it possible on the client side to be able to hold back Datasource updates until all the updates are ready for submission to the server?

And if so, is it possible to tell SmartGWT on the client side to discard pending datasource updates (e.g. rollback) if they haven't yet been sent to the server?

[Isomorphic]

There's a couple of mechanism for this:

1. queuing - see QuickStart Guide section on Queuing and also RPCManager.startQueue() - this is for putting together several requests that must be sent as a single HTTP request to enable a transaction

2. clientOnly DataSources - see DataSource.clientOnly - this allows you to have a shared, local set of data that several components work with. You can then submit all the changes at the end (after several user interactions) by inspecting DataSource.cacheData and comparing it to an original (issuing requests reflecting all changes is not automatic).

[bcamac]

I didn't know about that. Perfect.

thx
- BC