I'm constrained to using only the SmartGWT LGPL offering.
My understanding of the community-provided GwtRpcDataSource is that it does not provide any of the basic queue / batch / transaction / combined-operation features discussed in reference to RestDataSource in the quotes below. Do I understand that correctly?
Or is it that we get all of the above features if we go the GwtRpcDataSource route, by the underlying framework somehow providing all [or some] of the above features using non-batched / one-at-a-time / round-trip calls to fetch, add, update, remove?
Please clarify? Thank you in advance.
My understanding of the community-provided GwtRpcDataSource is that it does not provide any of the basic queue / batch / transaction / combined-operation features discussed in reference to RestDataSource in the quotes below. Do I understand that correctly?
Quote:
|
Originally Posted by Charles Kendrick
...
[more] |
Quote:
|
Originally Posted by Isomorphic
...transactions that mix operation types (like editing a grid and both updating and adding rows) or entity types (like inserting an order and it's related items).... [more] |
Quote:
|
Originally Posted by Isomorphic
...dozens of features that needs queuing to work: mass update (listGrid.autoSaveEdits:false), multi-row drag&drop, BatchUploader, large tree load-on-demand, master-detail saves, serverCustom validators, CubeGrid, many others... [more] |
Please clarify? Thank you in advance.