2 ms·
Sorry but REST is fine with forcing the client to maintain its own state (in fact it's pretty much assumed the client will, for any non-trivial application). Us
by wahnfrieden 15y ago
Sorry but REST is fine with forcing the client to maintain its own state (in fact it's pretty much assumed the client will, for any non-trivial application). Using hashes in this manner shouldn't require the server to maintain additional state. If I'm missing something here, could you please elaborate?
- extension 15y agoWell, an application has many kinds of state on many different levels. The sort of state that serves as the S in REST is the one that a client changes by requesting and manipulating representations of resources identified by URIs. An application composed of a single representation that implements the entire app with code-on-demand is not exploiting the REST architecture very much. Actually, even if the application is properly broken up into URIs, it's still not entirely RESTful because the "engine of application state" has become Javascript + secret protocol rather than hypermedia.
- wahnfrieden 15y agoAh okay I see now, code-on-demand as a primary method does run contrary to REST. Thanks for clarifying.