I'm researching SmartGWT's RestDataSource protocol to determine whether or not to recommend it to a customer for whom I am doing some consulting.
I came across a few comments like the following that have me puzzled and that I need clarification on. Please?...
Am I understanding correctly that what is being suggested in the above quotes, is that the best practice for the RestDataSource protocol is to prefer to reuse the same [non-distinct] URL for all dataURL setters as is done in the following example posted in another thead ...
Neither the RestDataSource FAQ entry nor the RestDataSource javadoc makes mention of any relationship between the dataURL property and the [I'm assuming] associated transactions / queues /batch requests feature.
Is there any such relationship? Is there any documentation anywhere that elaborates at all on this feature?
Thank you in advance.
I came across a few comments like the following that have me puzzled and that I need clarification on. Please?...
Quote:
|
Originally Posted by Charles Kendrick
...
Among other problems you've created:
|
Quote:
|
Originally Posted by Isomorphic
...
common blunders, such as...asserting that access to different entities must be at different URLs...which [prevents] transactions that mix operation types... ... [more] |
Code:
String URL = ...
RestDataSource jDS ...
...
jDS.setFetchDataURL( URL );
jDS.setAddDataURL( URL );
jDS.setUpdateDataURL( URL );
jDS.setRemoveDataURL( URL );
...Is there any such relationship? Is there any documentation anywhere that elaborates at all on this feature?
Thank you in advance.