Hi Andreas, thanks for your comments. On 03-10-2012 06:21, Andreas Krüger wrote: >> > We are not using websockets yet, but it seems a very good idea. > Thank you. > > But I'd leave the AJAX in, as a fallback for cases > where firewalls don't let UDP through. Company firewalls > typically don't.
When we talk about websockets, we are talking essencially about sockets over HTTP (and TCP), not UDP. I would have to implement kind of a "websocket ntp server" using NodeJS, for example, and a javascript client. The downside is that only the most recent browsers would support that: we are talking about HTML5, that isn't even standartized yet. To have UDP sockets inside browsers I think the only alternative (besides some proprietary alternatives from Microsoft, such as ActiveX) would be a Java applet. The other alternative is to provide a full program to be installed. I really don't see the difference, regarding security, in providing a full software to be installed or a applet to run inside the browser. > Greetings, best regards, > > Andreas []s Moreiras. _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
