04-07-2012, 12:27 PM
(This post was last modified: 04-07-2012, 12:35 PM by Dean Roddey.)
I can't really seem to find any coherent answer to this question. Clearly it seems HTML5 is pushing a lot of stuff to the client. But that exactly does a web server have to provide in order to support HTML5 clients? Is there any targeted documentation out there that addresses it purely from the web server side of things?
Presumably for automation purposes websockets would have to be supported I guess, to be able to maintain a persistent, two way communcations. But what exactly would a client side HTML5 application talk to via such a connection? Does it only use it for standard queries, and the other way is only for pushes of data? Is the connection between the client HTML5 app and whatever is going to push it data purely established through the URL it uses to create the ws connection?
Presumably for automation purposes websockets would have to be supported I guess, to be able to maintain a persistent, two way communcations. But what exactly would a client side HTML5 application talk to via such a connection? Does it only use it for standard queries, and the other way is only for pushes of data? Is the connection between the client HTML5 app and whatever is going to push it data purely established through the URL it uses to create the ws connection?
Dean Roddey
Explorans limites defectum
Explorans limites defectum