We have a REST application, which is mainly used by applications that should not support their state, so until now we have been calm "RESTFUL", not supporting state. We use Private / Public (similar to Amazon) for authentication. Currently, the client passes credentials for each request.
Now we have a new requirement when we need to maintain a state (or conversation). The client can be a Rich application or a handheld device. I am trying to find the best way to implement the state. We must pass the session id and maintain that id .. is this the best and only solution?
source
share