I'm not sure what a normal number of printers is. But within our corporation, some sites must have hundreds. Label and laser printers throughout the manufacturing and shipping areas really add up at even moderately sized companies.
If coded efficiently, it wouldn't be necessary for every jspprint process to continuously check for new jobs. It would seem more logical to have one process doing this and then signally the appropriate jspprint process. Though this is just speculation on my part. I don't know how it is actually structured. However it is being accomplished though, it seems like a sufficient solution. Printing has always been immediate up until this problem cropped up for a few printers accessed by our new server. -- Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
