grouper-dev - [ldappc-ng] request ids : doomdark uuid or ?

Subject: Grouper Developers Forum

List archive

[ldappc-ng] request ids : doomdark uuid or ?

From: Tom Zeller <>
To: Grouper Dev <>
Subject: [ldappc-ng] request ids : doomdark uuid or ?
Date: Wed, 7 Apr 2010 17:53:31 -0500
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; b=FG6u/5lGLDSFo1tkqhod4yUDuB0eHarvvoJuCO44+3YJdTx1x8cNnZmHNvFrMJ3CYR dS7r0/nf4u04NMTuH6CLv5wSmBekzUVZPUTrBkH5LXdKmo2xqUIvF2Iq9yGnhMyb6EWA AdylxC2jr8xrQunBEKD4e4FHbcKXbPtJn4yS8=

I'm looking for suggestions regarding unique identifiers. Ldappc-ng
needs to generate a reasonably unique identifier for each (spml)
request/response operation.

The request id will be included, of course, in the request/response xml :

<ldappc:calcRequest requestID='X' ...>

To make log reading easier, I've also used MDC to add the request id
to each log entry written while processing a request :

2010-04-07 17:44:59,960: X [main] INFO PSP.execute -
CalcRequest[id=stem:group,returnData=everything,targetIds=[],requestID=X]
2010-04-07 17:44:59,960: X [main] INFO PSP.execute -
CalcResponse[id=stem:group,status=success,requestID=X]

I have tentatively coded timestamp+request/response hashcode as the
request id because I liked the inherent sorting of a unique identifier
that starts with a timestamp, e.g. :

2010/04/07-17:49:56.439_349798490

A doomdark uuid looks like :

e3452b5e-4297-11df-a4e9-f505f1910c8d

So, what do you think, should the request id be doomdark uuids or ?

TomZ

[ldappc-ng] request ids : doomdark uuid or ?, Tom Zeller, 04/07/2010

List archive

[ldappc-ng] request ids : doomdark uuid or ?