spring - REST in workflow applications - where to keep the state? -
I tried to take a more detailed look on the rest - I love the spring too much, and I'm confused. The rest of the "resources" is fine for the original CRUD functions, but it seems weird for those applications which require the state to maintain, such as the workflow application I have read in one of the answers, it can not be found now , The state should be placed on the client. It seems strange: then does the customer stop cooking a request, and claims that he is in a state in which he is not? A way around it can be that the server sends the customer to sign his next state, and the customer then uses this signed status on his next request on the server. If someone has seen the "strong workflow app", then how is it actually done?
REST = delegate state transfer customer and server exchange of a resource status - Provide It is basically placed on the server and updated by the client (/ created / deleted).
The REST workflow is not odd for the app at all, although you can define it as the most difficult part when you design the remaining applications, and represent most of the resources. The resource is not just a unit from the database.
@NeilMcGuigan has mentioned that the rest of the samples are with the application workflow. One is on SpringstreamSide Channel on YouTube, where Oliver Gierke has submitted the application.
Comments
Post a Comment