Good idea Emmanuel. Permit me to extend on this a bit ...
Perhaps instead of getting really long OIDs you can use instead compute a hashCode from the suffix and just concat that as the
least significant OID term. For example:
Can be the following valid OID if the hashCode for org.tuscany.das.ldap.config.DASConfig.baseDN is 123456:
Bottle of wine...in Amsterdam...Sooooooure :-)
I think using ascii values is a great idea.
I'll stick it in the design guide.
Emmanuel Lecharny wrote:
> Ole, David,
> when I woke up this morning, under my shower, I had the idea I missed
> yesturday evening due to the bottle of wine I drunk ... - : why don't
> you use the ascii value of each character to code your OID, postfixing
> your PEN ? Something like :
> will be transformed to :
> 18.104.22.168.4.1.18060.0.4.X.2 (the prefix, where X is a number)
> .22.214.171.124. ... (111 = 'o', 114='r', 103='g', 46 = '.', etc)
> you will have very long OIDs, but this is not really a problem, and thy
> will be unique worldwilde because the prefix is assigned to your
> company, and you will have to manage the suffix (it's up to you to use
> correct packages...)
> On 4/5/07, *David Jencks* <firstname.lastname@example.org
> <mailto:email@example.com >> wrote:
> I would prefer to see a solution that mapped java objects to existing
> schemas, and perhaps has a way to generate schemas with oids, but it
> seems to me that autogeneration of something that is supposed to be
> worldwide unique and meaningful may cause more difficulties than it
> The worldwide OID will be enforced through the prefix (and management in
> the project :)
> For instance you'd need a way to reserve a unique PEN for each
> installation on which you wanted to run this stuff.
> That's very true. But if you use ADS in a company, then this company
> should have a PEN (at least in theory: as there are only 28389
> attributed PEN as of today ...).
> dunno, I'm kinda a beginner.
> you should be kidding ;)
> david jencks
> Emmanuel Lécharny
> www.iktek.com < http://www.iktek.com>