> What the author means with "transactional" is that WebSockets have no built-in request-response mechanism Its not HTTP and does not want to be HTTP. In WebS

> What the author means with "transactional" is that WebSockets have no built-in request-response mechanism Its not HTTP and does not want to be HTTP. In WebSockets the request/response mechanism is for one side to send a message and then the other side to send a message. If you want to associate a message from one side with a message from the other side put a unique identifier in the messages. If you really want the request/response round trip then don't use WebSockets. I would rather messages just transmit as each side is ready, completely irrespective of any round trip or response, because then everything is fully event oriented and free from directionality.