M
mihooper1
Guest
I have developed on .NET app that is a Network Management System (NMS) for a network of wireless devices. It continuously polls the remote wireless devices over the air and stores the real-time performance data in a local database on a laptop.
I would now like to develop a remote (client) app that has real-time access to this stored data, and which doesn't prevent (overload, block) the NMS app from continuing to collect remote data over the air.
I have begun by developing an async server (listener) that coexists within the NMS code on the laptop, based on the Microsoft Asynchronous Server Socket Example, and a separate client app that connects to the server over the internet and transfers a "transaction". This seems to work for single "transactions" (connect, transfer data, close connection). However, I want to poll the server constantly, in real time (i.e. ~1 poll per second) so that I can update the GUI of the remote app constantly.
So my very basic question is, what is the best approach from a networking standpoint to solve my problem? Do I use one connection (socket) request per poll (seems like a lot of overhead)? Or is there some other method of maintaining the connection indefinitely and continuously polling the server?
Basic stuff, I know. But that's where I am in my journey.
Guidance would be much appreciated.
Thx, MikeH
Continue reading...
I would now like to develop a remote (client) app that has real-time access to this stored data, and which doesn't prevent (overload, block) the NMS app from continuing to collect remote data over the air.
I have begun by developing an async server (listener) that coexists within the NMS code on the laptop, based on the Microsoft Asynchronous Server Socket Example, and a separate client app that connects to the server over the internet and transfers a "transaction". This seems to work for single "transactions" (connect, transfer data, close connection). However, I want to poll the server constantly, in real time (i.e. ~1 poll per second) so that I can update the GUI of the remote app constantly.
So my very basic question is, what is the best approach from a networking standpoint to solve my problem? Do I use one connection (socket) request per poll (seems like a lot of overhead)? Or is there some other method of maintaining the connection indefinitely and continuously polling the server?
Basic stuff, I know. But that's where I am in my journey.
Guidance would be much appreciated.
Thx, MikeH
Continue reading...