[Hpr] HPR Web Submission Form: Ready for [second] review

Ken Fallon ken.fallon at gmail.com
Wed May 22 00:30:18 PDT 2013

Reviving a dead post 

On Thu, 25 Apr 2013 15:17:32 -0400
epicanis+hpr at dogphilosophy.net wrote:

> As far as using md5 hash or similar things - I think I had mentioned
> that when Ken and I were having a (friendly and educational!)
> argument about UUID on the dev list back when I started in on this.
> Other than importing the UUID generation code (which was pretty much
> copy-and-paste) it didn't really make it any more difficult to write,
> so I didn't mind doing it that way anyway. The current alternative I
> have programmed in there as an option is timestamp (which would run a
> very small but nonzero risk of issues when two people uploaded at
> precisely the same instant) on the assumption that timestamp is at
> least a potentially-useful piece of information as well as suitable
> (for this use) as a unique ID.  md5sum of the uploaded file would
> have the same benefit (and could be fairly easily added as an extra
> ID option, with a little bit of refactoring of the "$uuid" variable
> handling since it would no longer just be "true or false") if that
> was desirable.
> (In practical terms on the server side, it probably doesn't make much 
> difference either way - so long as whatever the ID is, it remains
> unique enough to keep the uploads together but separate from other
> uploads during processing it should work equally well.  I do,
> however, think UUID is a tool of the devil. :-) )

OK Fair enough. You convinced me. I'll back down. (Twice in as many

Date in combination with the files md5sum should be fine to give
uniqueness. Two points: 
 - Dates should ALWAYS be in ISO8601 format.
 - You won't have the md5sum before the upload so you will need to
   rename once the upload is finished.


More information about the Hpr mailing list