4 ms·
The HTTP Query method is problematic: every request to a web server is by definition a query, so it is at a minimum poorly named. Second, most queries are not i
by indymike 5y ago
The HTTP Query method is problematic: every request to a web server is by definition a query, so it is at a minimum poorly named. Second, most queries are not idempotent and the return value can and will change. In other words, YAGNI.
- layer8 5y agoI don’t agree that "every request to a web server is by definition a query", similar to how not every SQL statement is a query. In terms of command-query separation, commands may return information about the execution of the command; the fact that they return something doesn’t make them a query. For example, an SQL UPDATE statement may return how many rows were updated, or that some error occurred; that doesn’t make it a query.
- indymike 5y ago> I don’t agree that "every request to a web server is by definition a query", Query is a synonym for ask. Request is a synonym for ask. We are now making request requests? This is redundant and is not needed.
- layer8 5y ago“Request” and “query” are not synonymous. A query is a request for information. A request can also be a request for action.
- indymike 5y agoYou just used request to define request. This isn't working.
- layer8 5y agoI didn’t, look closely.
- indymike 5y ago"A request can be a request..."
- layer8 5y agoI didn‘t define request, I gave examples of possible kinds of requests. There are requests for information, and there are requests for action (and there may potentially be still other kind of requests — it’s an open enumeration). My point is that queries are requests for information, and not requests for action. Therefore "query" is a proper subset of "request", and thus not every request is a query.