polling

I have a J2ME app running on my mobile phone(client), I would like to open an HTTP connection with the server and keep polling for updated information on the server. Every poll performed will use up GPRS bytes and would turn out expensive in the long run, as GPRS billing is based on packets sent and received. Is there a byte efficient way of polling using the HTTP protocol?. I have also heard of long polling, But I am not sure how it works and how efficient it would be. Actually the preffered way would be for the Server to tell the phone app that new data is ready to be used that way polling

I poll a lot of devices in network (more than 300) by iterative ping. The program polls the devices sequentially, so it's slow. I'd like to enhance the speed of polling. There some ways to do this in Delphi 7: Each device has a thread doing ping. Manage threads manually. Learn and use Indy 10. Need examples. Use overlapped I/O based on window messages. Use completion ports based on events. What is faster, easier? Please, provide some examples or links for example. Flooding the network with ICMP is not a good idea. You might want to consider some kind of thread pool and queue up the ping

I am trying to JSON.parse the array "data." I need to be able to pass the array as the root. { "data": [ { "type": "name", "id": "123" } ] } The response should look like this containing only objects. Zapier doesn't seem to work well with arrays. { "type": "name", "id": "123" } Shouldn't I be able to use a simple script to get the job done? EDIT: Essentially, you're going to want to override the post_poll method ( https://zapier.com/developer/documentation/v2/scripting/#polling ) in scripting so you can intercept the response of the API. After that, you just need to return a new object with

I am currently working on a c# .NET desktop application that will be communicating to a database over the internet via WCF and WCF Data Services. There will be many spots in the application that may need to be refreshed upon some interval. The easiest solution would be to just put these areas on a timer and requery the database. However, with thousands of clients connecting to the service layer and hence database, these operations would be very expensive to the server. What I have considered is creating an RSS feed that is polled by the client, and lets the client know when these particular

I'm trying to interface a large Scala + Akka + PlayMini application with an external REST API. The idea is to periodically poll (basically every 1 to 10 minutes) a root URL and then crawl through sub-level URLs to extract data which is then sent to a message queue. I have come up with two ways to do this: 1st way Create a hierarchy of actors to match the resource path structure of the API. In the Google Latitude case, that would mean, e.g. Actor 'latitude/v1/currentLocation' polls https://www.googleapis.com/latitude/v1/currentLocation Actor 'latitude/v1/location' polls https://www.googleapis