Transport: returns content-type/encoding
Closed this issue · 0 comments
tiero commented
The Transport protocol is a bit meaningless as per now, since the protocol used (ie. secure, insecure, onion etc..) can be detected from the canonical URL the clients consumes ie. https, http or .onion for hidden services.
Something more useful is to give possibility to signal to clients how the Messages are sent in an HTTP request
grpc
grpc-web
grpc-web-text
json
( this should be the minumum/mandatory encoding each provider MUST support, since is the supported in any platfomrs)