I’m looking for some software which can be installed on systems (Windows 2000 / 2003 / XP / Vista / 7) by subscribers and will automatically deliver requested content by launching their default web browser… in essence, a more intelligent, remotely configurable version of the DeskTopPop product.
Content delivery can occur:
1) after a pre-determined period of time (hours), or
2) at a pre-set UTC time
…provided that a period of recent and continued user activity has been detected.
For example, I might decide to have the user’s browser display a URL every 8 or 12 hours, provided that their computer is currently being used and has been continuously used for a short period of time i.e. 5 minutes.
I do not want to have browser windows open simply based on a timer so some monitoring of the keyboard and/or mouse will be required.
The actual current “waiting period” between browser launches and the required period of user activity (both in minutes) before triggering will be specified within the string returned by my server script which also specifies the target URL.
Please also note that the “waiting period” for “time delayed” URLs is the minimum time to wait since the previous URL was launched and is not cumulative i.e. if the waiting time is set to 8 hours but the user does not use their computer for 20 hours then only one URL should be launched (after the required “continuous use” period) and the next URL should not trigger for at least another 8 hours.
The utility should be unobtrusive to the user i.e. must install as an application but be invisible (nothing on the task bar, in the system tray or in the Alt-Tab window / Task Manager) during normal operation.
It is very important that the utility is able to work with all the major browsers and should not trigger false-positives for anti-virus / spyware / adware / malware systems – it should also be firewall-friendly.
A unique, system generated ID should be created during the 1st run process and passed to my server (when appropriate) during communications so that duplicate content can be avoided for each user.
The overall process should be something along the following lines:
a) at 1st run, generate and store a unique “user” ID in the registry, along with the current UTC time (indicating the “last launch” time)
b) immediately contact my server via an http post, passing the user ID
c) server will return the appropriate “waiting” and “continuous use” periods (both as minutes) followed by the “time delayed” URL in the following format: 10|3|yahoo.com
– the returned URL, waiting and continuous use periods should be stored in the registry
d) immediately contact my server via an http post, passing NO user ID
e) server will either return the UTC “activation time” and “continuous use” period (as minutes) followed by the “time specific” URL in the following format: 200911281457|2|google.com OR a “nothing scheduled” instruction in the following format: ||
– if a time-specific instruction was returned, the URL, UTC activation time and continuous use period should be stored (or replaced) in the registry (separately to the “time delayed” information)
f) monitor the time passed since 1st run / last URL launch and most recent period of continuous user activity until:
i) 60 minutes have passed, in which case go to step d)
ii) the pending “time delayed” URL should be launched, in which case go to step g)
iii) the pending “time specific” URL should be launched, in which case go to step h)
g) launch the “time delayed” URL in the default browser, update the “last launch” time in the registry, then go to step b)
h) launch the “time specific” URL in the default browser, update the “last launch” time in the registry, then go to step d)
Notes:
1) the initial “time delayed” URL should not be launched until “waiting” period minutes after the UTC time stored during the 1st run
2) “time specific” URLs should be ignored (i.e. not stored in the registry) unless the launch time is in the future
3) “time specific” URLs take precidence over “time delayed” URLs so if a “time specific” URL is scheduled to launch within the next 24 hours (note that it may have been scheduled for several days already) then any pending “time delayed” URL launch should be postponed until “waiting” period after the “time specific” launch takes place
4) the registry location should be configurable to allow multiple copies of the system to run concurrently and deliver different scheduled content
The following PHP script can be used for testing purposes:
<?PHP
if (isset($_REQUEST['id']))
{
echo “10|3|yahoo.com”;
}
else
{
if (rand(0, 1) == 0)
echo gmdate(“YmdHi”, time() + 480) . “|2|google.com”;
else
echo “||”;
}
exit;
?>
Delphi is the preferred development language but not a necessity.
All, fully commented, source code should be provided.
Any 3rd party code included in the project must be public domain / GNU or similar i.e. no cost for commercial use.
Size and speed / simplicity of installation is important so any potential 3rd party downloads / code extensions i.e. dotNET, are not acceptable.
Confirmation of successful testing on Windows 2000, 2003, XP, Vista & 7 is a requirement.
