comment on

In other words, you want to provide something along the lines of DBI's catalog methods. So, what I would do is the following:

Define a mechanism for creating objects without having to know the whole class name. Something like DBI's connect where the DBD is figured out from the DSN. I would suggest using various items:
- Manufacturer
- Model
- IP address / Windows address
Remember - you still have to talk to this printer, so you need to be able to specify that it is this printer that that object is representing. Also, are there ways to auto-detect what manufacturer/model a given printer is if you know the IP address?
Define the interface by which you interrogate the object. Instead of using your attrs() method, I would actually have the Printer::Status::Acme::x1000 class provide methods. So, that way, you can say something like
```
if ($printer->can( 'serial_number' ))
{
    print "Serial Number: ", $printer->serial_number, $/;
}
[download]
```
Provide a set of guidelines for authors, similar to the DBD-author guide that tbunce created. You also will want a mailing list. Then, when someone wants to write one of these, they will come to the mailing list and be educated in the ways of the architecture. That's how you make sure you don't have serial_no() vs. serial_number() vs. ser_no().
If there are multiple ways to access the information, the PSD (printer-status definition) author should be able to support them, but provide a useful default. Then, the user can specify in the connect() clause which connection method.

You really need to study how DBI did things. I'd also suggest using the namespaces PSI (printer-status interface), PSD (printer-status definition), and PSIx (other printer-status modules).

Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

In reply to Re: Strategies and suggestions for a printer status hierarchy by dragonchild
in thread Strategies and suggestions for a printer status hierarchy by grinder

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.