Rapid composite resource definition and implementation (using ResourceStub) · Issue #23 · oofp/Beseder · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
List of resource states (this states are used as state tags)
List of supported requests
List of supported requests for every states
Possible state transitions (optional)
This info is is used to derive "resource stub" resource which
allow resource implementation to inform client about state transition. The IMPORTANT: state transition by resource implementation is three phase
a) implementation asks to change
b) change become visible to client (state change pending)
c) state changed
After a) and up to c) resource implementation may get requests that were allowed for the previous state (race condition) In this case the state transition is rolled back and resource implementation need to handle new request while having option synchronously to set new state (Still need to think how). In this case resource transition happens along with state transition. Resource stub is state is changed. Request invoked is state of ResourceStub and implementation must reset invoked flag. So alternative approach (nice!) maybe to allow direct (synchronous) state change when handling the resource.
The implementation consists of the following flows (STransData)
a) initialization, that creates the resource from () to single resources set that contains at least ResourceStub
b) event handler (handling of requests (state changes of resource stub) and state changes from other resources)
c) cleanup script (from static state to ())
Transitions and request results will be derived from these three flows
TH will be employed.
The text was updated successfully, but these errors were encountered:
oofp
changed the title
Express composite resource definition and implementation
Rapid composite resource definition and implementation (using ResourceStub)
Feb 29, 2020
Uh oh!
There was an error while loading. Please reload this page.
This info is is used to derive "resource stub" resource which
a) implementation asks to change
b) change become visible to client (state change pending)
c) state changed
After a) and up to c) resource implementation may get requests that were allowed for the previous state (race condition)
In this case the state transition is rolled back and resource implementation need to handle new request while having option synchronously to set new state (Still need to think how). In this case resource transition happens along with state transition. Resource stub is state is changed. Request invoked is state of ResourceStub and implementation must reset invoked flag. So alternative approach (nice!) maybe to allow direct (synchronous) state change when handling the resource.The implementation consists of the following flows (STransData)
a) initialization, that creates the resource from () to single resources set that contains at least ResourceStub
b) event handler (handling of requests (state changes of resource stub) and state changes from other resources)
c) cleanup script (from static state to ())
Transitions and request results will be derived from these three flows
TH will be employed.
The text was updated successfully, but these errors were encountered: