for most kind1 clients I see the benefit of websockets. But when a single request is needed, I think http is just simpler.
Is it true nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 that you "don't like" http? If so, what's the rationale?
I use both in my web client. https has a lot of overhead for each request. Perfectly fine for responding to user requests but not great for real-time event-driven behaviour. Sockets is better.
my understanding is that if the requests are less than 3, or are distributed over minutes, than http.
Else websocket.
wdyt?
Yep. Good old https rest api does the job for 95% of the functionality. However, when you need async event driven stuff, websockets is the way to go. For example, when I am waiting for a Lightning payment, I prefer to use a websockets to push the event through when it comes rather than poll for it. A lot less stress on the server.
HTTP has too many ways to do things.
For example, to communicate some data to the server you can use:
- subdomains
- URL paths
- URL query strings
- headers
- body (which can be encoded in multiple ways and supposedly you have to tell the server what you're using with a header)
And when you get a response you have to check these places for information
- status code
- headers
- if it's a redirect you have to make another request and repeat the process
- body (which can be encoded in multiple ways and supposedly you have to check the headers to find out, and yet it may be incorrectly encoded)
