Harry, I'm a little vague on where IPP is right now, so bear
with me. But...
The prtChannelInformation data is just supposed to provide a
"bootstrap." In the case if IPP, just enough information to
fire up an IPP connection -- then ask the IPP service what its
more detailed characteristics are. The rule was, essentially,
"if you don't need the information to establish the
protocol-specific connection, it doesn't belone in the
prtChannelInformation."
This two-step process was always explicit in the design of the
prtChannelInformation (at least in my mind). It wasn't, for
example, intended to be something like the IPP directory entry,
that attempts to characterize the service.
So I don't see any reason to change Tom and Ira's chIPP
definition.
David
:: David Kellerman Northlake Software 503-228-3383
::david_kellerman at nls.com Portland, Oregon fax 503-228-5662