> b) the primary issue is being able to determine the printer status, i.e.
> did the connection fail because the printer is down or just busy. One
> simple solution is to have a printer read on a UDP port dedicated to
> returning a status summary whenever it receives a request on the port. If
> the incoming bytes are limited and have simple options, the printer will
> never be tied up for long on each transaction and will always be able to let
> a client know if it is alive and whether there are any problems. Then if the
> connection fails, it is because the printer is down or the IP address is bad.
Sounds like a fixed SNMP query. Why don't we just use
SNMP and the Printer MIB for this kind of thing?
...jay
----------------------------------------------------------------------
-- JK Martin | Email: jkm@underscore.com --
-- Underscore, Inc. | Voice: (603) 889-7000 --
-- 41C Sagamore Park Road | Fax: (603) 889-2699 --
-- Hudson, NH 03051-4915 | Web: http://www.underscore.com --
----------------------------------------------------------------------