Hi.
We are building a streaming server for a client. For the connection layer, we will use a Socket instead of HTTP and will stream instead of sending chunks like we do now.
In the past, I've done this by simply using a
thread pool and a regular
Java socket. We can still continue on that way but before I do, I want to understand what websockets give me that a socket Socket does not (if anything). I understand that web sockets allow browsers to communicate with webservers over sockets. If my client is a stand alone app and (not a browser) but does need to connect to a Socket over the web, does a websocket give us any advantage?
Thanks for any thoughts you may be able to offer.