worker

I'm writing code that need to run only when there is no human activity on the PC, like when the screensaver is running. Any suggestions on how to do this in c++ under windows? @talnicolas, simply to use unused resources, how many times people leave the computer on but they are in another place? You can use GetLastInputInfo to check how long the user has been idle (not moved around the mouse or typed something on the keyboard) and SystemParametersInfo to check if a screensaver is active. Example #define WINDOWS_LEAN_AND_MEAN #include <windows.h> #include <iostream> // do something after 10

C# 2008 I am using the code below to login to a softphone. However, the login progess is a long process as there are many things that have to be initialized and checks to be made, I have only put a few on here, as it would make the code to long to post. In the code below I am checking if the CancellationPending if the CancelAsync has been called in my cancel button click event, before doing each check. Is this correct? Also if the check fails I also call the CancelAsync and set the e.Cancel to true. I would like to know if my method I have used here is the best method to use. Many thanks for

I am implementing a worker pool in Java. This is essentially a whole load of objects which will pick up chunks of data, process the data and then store the result. Because of IO latency there will be significantly more workers than processor cores. The server is dedicated to this task and I want to wring the maximum performance out of the hardware (but no I don't want to implement it in C++). The simplest implementation would be to have a single Java process which creates and monitors a number of worker threads. An alternative would be to run a Java process for each worker. Assuming for

I work on a web application that is a multi-tenant cloud based application (lots of clients, each with their own separate "environment", but all on shared sets of hardware) and we're introducing the ability for a user to batch up work for later processing. The types of batched work really isn't important, it's just of sufficient quantity that doing it without a work queue isn't really practical. We've selected RabbitMQ as our underlying queue framework. Because we're a multi-tenant app, we don't necessarily want clients to be able to cause lengthy queue process times for another client, so one