2 ms·
> I'm not sure what you mean by "isn't rooted in HTML/http concepts". Yeah, sorry, what I meant was that it has a protocol spec (eg. as an RFC or equivalent),
by tannhaeuser 7y ago
> I'm not sure what you mean by "isn't rooted in HTML/http concepts".
Yeah, sorry, what I meant was that it has a protocol spec (eg. as an RFC or equivalent), and not just one canonical client and server impl, resp., and aligns with HTTP's concept of a network entity, URL, or even ETag, etc., because that'd be natural for my use case.