WRS ODATA transaction
Hi team
Do a search for 'transaction' in the WRS 2.2 manual (link 1 below). I get 8 hits. In particular, the 8 page section 'Processing HTTP Requests for OData URLs' starting at p.45 is necessary reading. I wish it contained an example.
Clearly the transaction mechanism is intended to guard POST requests. And see 'Change sets do not support the GET operation.' on page 80. Now there is an example, thanks!
Now my question: suppose that you need to make two GET requests in succession for a report, and Windchill data can change between the requests. What algorithm can be used to ensure consistency?
Perhaps some sort of consistency checking, followed by a retry?
REST principles are important (link 2 below)
cheers -- Rick
https://stackoverflow.com/questions/33060968/rest-and-transaction-rollbacks

