Currently what we have is an applet communicates via FTP, Sockets and HTTP messages from our hardware and servers. I have been asked if we can skip the applet and just go with dynamic web pages and javascript displays browser. I believe this is possible because it is my understanding that a browser can only display the response to the request that started it, whereas our application needs to display data, which comes from hardware , Which is sent only when the sensors are tripped. / P>
I used to think of using AJAX to choose hardware from time to time, but I believe the same basic security restriction allows me to vote different hardware devices with different addresses Will stop. I can decide that different hardware devices send all updates to the server but it will bring a big change in the way we are currently configured. There is also a question of performance - this is a national application with hundreds of tools, which produces millions of incidents per day. I have to be able to answer in 3 seconds, so I have to vote the hardware often (1 second or less) to maintain that level of performance.
So am I correct in my understanding of web applications?
This is possible. First of all you can right that a browser does not connect directly to other servers using AJAX. If these other servers are actually some hardware devices, then I'll call it an advantage. You need a server to get all the traffic.
However in modern browsers and servers you can use the usage, S and other techniques to access the data from the server. Actually you have an open HTML connection to the client and whenever the server has some data, it sends it immediately without any delay. This is a big improvement over voting every few seconds - you avoid system delays and extra burdens.
You have more defense in Java's land.
Comments
Post a Comment