Interresting thoughts, though the PWG is not trying to create
a truly native SBP-2 printer profile. As I think about it, I
don't know of _anyone_ that is.
Your thoughts imply that:
- a truly native SBP-2 printer profile has a standard "printer"
device model with standardized status info.
- the printer is being driven by an intelligent agent which is
aware of command boundaries. So it's either driven directly
by the printer driver, or by a command-set-intelligent spooler.
By the way, I don't want my printer to throw away the rest of
the data when it runs out of paper. I want it to tell me it's
out of paper, wait for me to put paper in, and then continue
printing. :-)
> As part of a truly native SBP-2 printer profile, I would expect
> to include a sequence number or something in the ORB command,
> so that a target can be sure not to execute the same command
> twice. I would also allow a target to abort at any point it
> likes and communicate this to the initiator. For example,
> "I ran out of paper between commands 4 and 5 in ORB 1129
> and I flushed further execution. Tell me what to do now.".
>> --------------------------------------
> Eric Anderson ewa at apple.com> Apple Computer, Inc. 408-974-8187
> --------------------------------------
--
Greg Shue
Hewlett-Packard Company
Office Products Division gregs at sdd.hp.com
----------------------------------------------------------------