Well, 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.
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.