3 ms·
Sigh, maybe Client-Server or Remote Data Access?: "3.4.7 Remote Data Access (RDA) The remote data access style [131] is a variant of client-server that spread
by e12e 11y ago
Sigh, maybe Client-Server or Remote Data Access?:
"3.4.7 Remote Data Access (RDA)
The remote data access style [131] is a variant of client-server that spreads the application state across both client and server. A client sends a database query in a standard format, such as SQL, to a remote server. The server allocates a workspace and performs the query, which may result in a very large data set. The client can then make further operations upon the result set (such as table joins) or retrieve the result one piece at a time. The client must know about the data structure of the service to build structure-dependent queries."
http://www.ics.uci.edu/~fielding/pubs/dissertation/net_arch_styles.htm#sec_3_4 http://www.ics.uci.edu/~fielding/pubs/dissertation/net_arch_...
REST is a very specific architecture, with very specific constraints. Not everything is REST, not everything should be REST. And there's certainly no reason to call things REST, if what one means is simply a client-server application over HTTP. But if what one is building is "just" client-server, perhaps HTTP isn't the best transport.