Dear developers!
In many situations it will be very useful to have one universal oid space instead of itemid's, hostid's, groupid's sets, which can (and in common case - it always does) intersect.
I suggest to switch to bit-encoded scheme, where first (rightmost on Intel architecture) 8 bits of each oid are encoded objectClass and the rest is local ID of the object inside its group. Why first 8 bits, not last? Because of the different size of the word on different architectures and to save some space on PHP side, because in string representation ID's with objectClass in leftmost position will be "too long".
So every oid will be unique and descriptive. I think, this conversion will not be too complex to implement.
Thanks!
In many situations it will be very useful to have one universal oid space instead of itemid's, hostid's, groupid's sets, which can (and in common case - it always does) intersect.
I suggest to switch to bit-encoded scheme, where first (rightmost on Intel architecture) 8 bits of each oid are encoded objectClass and the rest is local ID of the object inside its group. Why first 8 bits, not last? Because of the different size of the word on different architectures and to save some space on PHP side, because in string representation ID's with objectClass in leftmost position will be "too long".
So every oid will be unique and descriptive. I think, this conversion will not be too complex to implement.
Thanks!
Comment