kiitos

51 ms·

811.
by kiitos 3y ago
It isn't. Batching means combining multiple logical operations in a single physical request. HTTP/2 muxes N logical requests over 1 physical connection, which is good, but the application will still process requests independently.
812.
by kiitos 3y ago
This suggests you just don't grok HTTP semantics.
813.
by kiitos 3y ago
Of course, there are tons, they're generally called IDLs (interface description languages), common examples are Protobufs, Avro, Thrift, etc. They're not hugely popular for web services largely because the web was designed to avoi
814.
by kiitos 3y ago
> If your edge data model is ... more complicated than [a read-dominated workload] you're probably doing it wrong Huh? There are a huge number of applications that require writes at the edge. This access pattern in no way indicates
815.
by kiitos 3y ago
You probably wouldn't use a PUT for anything like this, true. But if you're going to mark a message as "seen" in a way that would impact a UI widget like an "unread notifications" red dot, then you almost certa
816.
by kiitos 3y ago
This article defines REST incorrectly, and doesn't seem to understand the concept of HTTP methods, calling them verbs (arguably fine) and types (huh?) seemingly arbitrarily. Methods are a core part of HTTP -- just because you can'
817.
by kiitos 3y ago
Well, caching a response to a GET request is always going to be subject to variables like Etag and other hashes of the request, time limits, etc. which all ensure that responses, even old responses, are never _wrong_, they're at worst
818.
by kiitos 3y ago
They do not.
819.
by kiitos 3y ago
Users don't dictate terms, though. How my API works is up to me. If I target use cases that prefer truncation of messages to errors, then surely it's acceptable for me to build it that way, right? I'm not saying it's a g
820.
by kiitos 3y ago
Yes, that's true. What makes you think that the API described in this post would be subject to those kinds of legal and/or regulatory requirements? Could it be the case that the author knows prima facie that no such requirements
821.
by kiitos 3y ago
Go has a concept of a byte, and a concept of a rune, but no concept of a char.
822.
by kiitos 3y ago
The message in question is being delivered to an end-user device, and is not expected to serve any purpose other than being displayed on a screen. In this context, it seems totally reasonable to truncate overly-long messages.
823.
by kiitos 3y ago
The vast majority of software written is private code that serves specific business requirements. That's not always going to be services, but it often is. Coreutils is statistically zero percent of all software.