From: <pa...@rc...> - 2001-01-02 06:03:13
|
Jarl Friis wrote: > I can imagine the usage of one OID is the same among different devices, > but what I ment was: the *set* of OIDs is not the same among different > devices, right? hence the OID-table is device dependent. So it would > probably be in order to make a global table of all known OIDs, and then > for each device make a table (representing a subset of the global > list) that tells which OIDs the device can use. the device-specific subset > could eventually just be a list of indexes to the global table. Yes, strictly speaking, the *set* of OIDs may vary between devices, depending on which devices you're talking about. One could certainly expect devices in the same series to support the same set of OIDs, for example, G55/G85/G95. There is also a fair amount of overlap between groups of series. For example, on http://hpoj.sourceforge.net/suplist.shtml, the devices which say "not yet" under "Scan" all use PML to set scan parameters and start scanning. The core set of scan OIDs is pretty consistent across this class of devices, but there are also a few device-dependent scan OIDs which may not be very important for our purposes. The same is true for devices which support PC-assisted fax-send, fax-receive, and copy. Actually, I'm not planning on having a master OID table compiled into the code the way it is with ojlib. Instead, applications will pass #defines for the OIDs they need to PTAL, which will dynamically build a list of OIDs that the application is actually using. That way, only the OIDs that are actually used are compiled into the application, and they should be compiled in only once as long as they are "created" in only one place. (I think this will make more sense once I have some working code to show you.:-) David |