in fact, the point of the "Print Server" configuration, and all the various files and paramters providing links between boxes (CPUs) is to support off-loading tasks from the production environment. I know it can make configuring Taskman seem unnecessarily complex (and confusing), but ther is a method to the madness. The General Processor configuration is simple and easy to understand, but lacks this benefit.
I am undecided about allowing unlimiterd creation of jobs. Certainly, it make sense that the OS will be able to handle scheduling and reource allocation much more efficiently than VistA ever could. Also, bear in mind that VistA has been around for a long time, and has run under some operating systems that are, well let's just say minimal, by today's standards. But even on modern operating systems, there is a place for resource limits. Starting a new job for each inbound HL7 message could be bad news. (Has anyone noticed that I keep saying we badly need asynchronous I/O?) === Gregory Woodhouse <[EMAIL PROTECTED]> "Judge a man by his questions not his answers." --Voltaire ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members