MasonOfWords

24 ms·

1. 1.▲
   by MasonOfWords 10y ago

   Service interfaces should be well-typed. Almost by definition, the cost to update a service interface will be a fraction of the time associated with updating its consumers and testing their integration. Dynamic types can lower a part of t
2. 2.▲
   by MasonOfWords 10y ago

   The FUD here is a bit ridiculous. Writing movie scripts in YAML using unquoted strings? That's pretty contrived. Using literal style is easy when it is potentially needed (e.g. programmatic output), and any decent editor can highligh
3. 3.▲
   by MasonOfWords 11y ago

   In OData, these problems are solved by: * Client communicate their desired projection and page size (via $select and $top query string parameters), which can then easily be mapped by the service into efficient calls to the underlying data s
4. 4.▲
   by MasonOfWords 11y ago

   I don't know, there are some tradeoffs there. Their sample appears to be "nearly JSON", which doesn't seem too helpful. Being close to but noncompliant with a standard doesn't bring anything but confusion. And it
5. 5.▲
   by MasonOfWords 12y ago

   I think that part of the problem with REST implied by the article is that it is purely request/response, rather than supporting full bidirectional communication. To me the term "temporal coupling" is skipping some details, si