looks like fully workable solution
Okay, I'm gonna work on this. The server admin is skilled and I am more than sure that I can place a chron script on the remote. Their help page already has directions on how to do so. Writing the servelet side of the action is well within the skills that I have recently accomplished. What using your apporach does in my problem domain is remove the need for a remote/local traffic pair. I will have to do get-going work on shell scripts generally and as well actually writing the script, it would call something like
I saw the semicolon mentioned as a later standard for name value separators, that may not be correct nor current practice, that would be part of my studies. I can find the RFC within minutes, but given your skills a citation of the relevant RFC would not hurt.
I studied the sample code on the subject of the post title from java tips, what I can do is have it remotely generate SecureRandom (Java 2 Platform SE v1.4.2), something I had wanted to be able to do anyway. I can setDaemon(true); and setPriority(low); in the initializer. By doing this, I remove the barrier of trying to transmit randomizing material. That would allow all the protections that I can achieve with my current skills to occur solely on the server, they already have some serious security tools in place and functional.