Interesting. I caught up on this thread because I was the person who pointed Tim towards Websockets / SSE for his ongoing projects. I also believe in only using the most basic tool for the job, but do you think that it's less complex for clients to make one query, wait until it's resolved and then make another?

I think that EOSE is a fairly useful tool to combine those two requests into one, and any half-decent implementation can send a CLOSE after that point if they aren't interested in subscribing.