http is good.
(and also a socket, just with comm schema/protocol and connection closed after a response, which poses significant overhead for a new connection per request)
Login to reply
Replies (2)
It depends on the usecase and thats why i'm saying we should have both
indeed