Some questions about a couple of your proposed prtChannelInformation
specs:
> Here are proposed prtChannelInformation definitions for selected
> PrtChannelType values:
>
> chLPDServer(8), -- ...
> -- prtChannelInformation entries:
> -- printer queue name
> -- name: QUEUE, mandatory, single value
> -- value is the ASCII queue name as
> -- described in RFC 1179
How do you propose specifying multiple LPD queues? Should the implementor
provide multiple channel type entries (in which the singular QUEUE name
is specified on a per-entry basis)? Or should the QUEUE keyword be allowed
to have multiple values?
Also, we had (privately) discussed the notion of defining "well-known"
LPD queue names to effect common services types, for example:
"Raw" The print job data is processed "as is" with no translation.
"AutoCR" Any linefeed character encountered in the job data stream
will have a carriage return character automatically inserted
after the linefeed character.
Should we bring up this topic now while the MIB spec is in flux?
> chDECLAT(32), -- ...
> -- prtChannelInformation entries:
> -- port name
> -- name: PORT, optional, single value
> -- service name
> -- name: SERVICE, optional, single value
> -- Exactly one of port and service must be
> -- specified.
The last sentence is a bit confusing. Are you saying that only ONE of
the defined keywords can exist in the value? Actually, the text makes
it sound like a chDECLAT channel type MUST specify either the PORT or
the SERVICE; that is, neither keyword is really optional. Can you clarify
this?
...jay