RE: UUIDs in 2.0
From: dean gaudet [mailto:[EMAIL PROTECTED]] Sent: 14 September 2001 12:45 On Fri, 14 Sep 2001, Sander Striker wrote: Isn't there an apr_get_current_time() that is thread safe? apr_time_now()? that's not the point. i'm guessing you haven't read the code i'm referring to. -dean Did now :) Ok, it seems like most of the reference implementation ideas have been duplicated. The get_current_time function is indeed not thread safe... Hmmm, wrapping those statics in mutexes is a major slowdown... Ok, dean, suggestions? :) Sander
Re: UUIDs in 2.0
On Friday 14 September 2001 02:57 am, dean gaudet wrote: On Fri, 14 Sep 2001, Sander Striker wrote: I believe uuids are modelled after dcerpc uuids. There is a Paul Leach draft on uuids floating around on the net. I would appreciate it if this could stay, it would benefit other projects aswell. i'm not arguing to get rid of uuids, i realise they're in widespread use. i don't have to like them though :) - get_current_time() is not thread safe Use the apr equivalent? the code i'm referring to is in apr, and it's not thread-safe. I believe Sander meant that we should re-write that code to rely on the thread-safe APR time routines instead of the ones currently in that function. Ryan __ Ryan Bloom [EMAIL PROTECTED] Covalent Technologies [EMAIL PROTECTED] --
