JMP Mail Archive: RE: JMP> Resource Table - Missile or Camera
RE: JMP> Resource Table - Missile or Camera
Tom Hastings (
hastings@cp10.es.xerox.com)
Mon, 31 Mar 1997 14:57:38 PST
At 09:42 02/14/97 PST, Harry Lewis <harryl@vnet.ibm.com> wrote:
>Ron wrote:
>
>>The more I look at the resource table, the more I agree with Tom
>>that it is a "win-win" situation. A DPA printer can present every
>>possible parameter and a real-world printer can present only the
>>useful values it can access. All of this without a large number
>>of objects in the MIB.
>
>I agree! The resource table, with resource type enums, is turning
>out to be a great idea.
>
>One thing I'm finding is that Resource Name seems to be redundant
>with information that should already be in the Printer MIB. I wonder
>how useful resource name is. If we're trying to name a resource like
>OutputBin (3) "Big Bin" - then the name is surely in the printer MIB
>and a server implementation would not be representing this resource.
>If we're trying to get fancy and say MediaType (Paper) "Hillary's
>Pink LetterHead", I really doubt any accounting application will
>be this sensitive. I think a Paper enum (Grade-A, Grade-B etc.)
>for charging purposes is more practical.
>
>Anyone else vie for eliminating Resource Name?
>
>Again, otherwise, I really LIKE the resource table!
So now we have just the following objects in the Attribute table:
The Attribute Group (Mandatory) 78
jmAttributeTypeIndex 80
jmAttributeInstanceIndex 81
jmAttributeValueAsInteger 81
jmAttributeValueAsOctets 82
Ok?
>
>Harry Lewis - IBM Printing Systems.
>
>
>
>