Kevin Baker wrote:
> Great!
> 
> This is exactly the concept we discussed in the thread
> last year. Although we talked about more detail, I think
> that this will be sufficiently unique to avoid collisions.
> 
> My only suggestion would be that the code to generate the
> GUID be kept in a function that can my easily modified
> system-wide. This will allow for updates later if we find
> the GUID needs to be slightly different to maintain
> uniqueness. I'm guessing you've already done that.

You guessed right :-): /extract to function/ is my favorite
code-refactoring.

The main limitation wrt GUID is the fieldsize. My current setup will fit
snugly into a bigint. Not much room left though.


> 
> Thanks for jumping on this... I've started a couple times
> but am really a Java developer and not too familiar with
> the DBMail code.

Well, I *was* mainly a python/shell/php developer myself. But I've been
hacking on dbmail for something of a year now, and I must say C grows on
you. I just miss OO :-(. But pushing bits and bytes around on the bare
metal has its glories. Reminds me of the days I was hacking ASM on my
old C64.


-- 
  ________________________________________________________________
  Paul Stevens                                      paul at nfg.nl
  NET FACILITIES GROUP                     GPG/PGP: 1024D/11F8CD31
  The Netherlands________________________________http://www.nfg.nl

Reply via email to