P1394 Mail Archive: P1394> Re: Native SBP-2 Printer Profile?

P1394 Mail Archive: P1394> Re: Native SBP-2 Printer Profile?

P1394> Re: Native SBP-2 Printer Profile?

Greg Shue (gregs@sdd.hp.com)
Fri, 20 Feb 1998 12:15:40 -0800 (PST)

>
> I don't believe the entire printer model has to be standardized,
> we just need a way to communicate basic operational steps, such
> as start a job, report status, report errors, etc. Within such
> a framework, and number of formats, protocols, etc, are possible.

Agreed. The PWG has already agreed (?) that a print job is
a separate data path than device status. No one has raised
the topic of reporting formatting errors. I don't know if
it's a general issue or not.

> If after running out of paper you'd like to load more and continue,
> you can just requeue the same ORB and let the printer pick up from
> where it left off. (I would design the native printer profile so
> that the printer can remember where it was in that ORB, and not
> execute the same parts twice.) My statement shouldn't be read to
> imply that any error causes a total shutdown - just that the
> printer will wait for further instructions.
>
> --------------------------------------
> Eric Anderson ewa@apple.com
> Apple Computer, Inc. 408-974-8187
> --------------------------------------

I was trying to avoid the printer having to verify that the
same ORB was requeued and remembering the offset into it. I've
always had the impression that it would be more problematic
than breaking the data up into transport-level blocks. Perhaps
you can convince me otherwise. Would you try?

-- 
Greg Shue
Hewlett-Packard Company
Office Products Division			gregs@sdd.hp.com
----------------------------------------------------------------