2 ms·
And I think it's a good idea. Take HTTP for example. It is much more than its protocol. Freeing it from those details means that what is valid today: GET /
by sph 3y ago
And I think it's a good idea. Take HTTP for example. It is much more than its protocol. Freeing it from those details means that what is valid today:
GET / HTTP/1.1
Host: example.com
Could have the same semantics in any format:
{
"method": "GET",
"version": "1.1",
"headers": [{"name": "Host", "value": "example.com"}]
}
Of course a server accepting the former won't be able to communicate with the latter, but that's just an implementation detail that Willow does not want to commit to at this stage, and does not make it any less complete. Just a bit impractical.
- sillysaurusx 3y agoThe history of cryptography failures suggests that it’s better for a protocol to be opinionated and complete rather than open ended.
- ianburrell 3y agoFormat agnostic layers are a good thing. HTTP2 depends on it with different encoding but same meaning. But have to choose some encoding for communication to happen. Otherwise it is a meta protocol.