Polling does not have to be an immediate request/response. See long polling:
https://www.pubnub.com/blog/2014-12-01-http-long-polling/ With websockets your are going to have a connection open all the time anyway, so long polling is no more resource intensive. I would not use it for the public web, but for 50 to 100 clients on a local network it seems pretty straight forward. John DeSoi, Ph.D. > On Jan 15, 2019, at 3:40 PM, Stephen J. Orth <[email protected]> > wrote: > > This is just "polling" logic and won't work for us, which is why I am asking > about web sockets. > > In our world, when a machine goes down we have to immediately contact the > browser managing the machine. In polling logic, it would mean we only check > every X interval. Before anyone says "well just make it a short interval" > take into account I may have 50 - 100 browsers all polling continuously. > This is a lot of traffic which simply asks the server "anything for me". > Keep in mind 99% of the time the answer from the server will be no. This is > a lot of overhead for the 4D Server to be dealing with continually. > > It's much more efficient, considerably less taxing, to just have the server > push a request to the shop floor browser only when some action is required... ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
