>>Is there any equivalent to javascript's document.lastModified?
>>Can create a "serial number" based on the date of submission, then
>>rearrange by fields to a sortable ID, eg 2007.05.15.23.53 for a tip
>>created yesterday at 23:53.
>>Don't need dots, or hyphens, or anything, as 2007051523353 would be
>>fine, too. The odds of having 2 tips be submitted in the same minute
>>would be remote.
>I don't think so. A minute is sixty seconds, and sooner or later we'll
have
>two different users submitting tips less than sixty (or even thirty)
seconds
>away from each other. Even adding the seconds to the ID doesn't clear
the
>problem, it lowers the probability but doesn't make it zero. With
enough
>Vimmers adding tips, sooner or later there'll be a clash.
Okay, so can probably have something like
if exist N
N++
to make sure that when "naming"(?) a tip, there's no name-collision.
Gotta be *somewhere* to put in the smarts to avoid name-collisions, no?
Or if each tip is a file, then a name-collision would be attempting to
overwrite an existing file, and a cookie or something could make sure
that doesn't happen, ie, only write the actual tip you're working on.
Like I said, I have no idea about the mechanisms in use to create wikis
or edit entries, etc., so I'm just flinging ideas at the wall to see
what sticks, if anything. Someone more versed in wikiing might put 2+2
together and say, "Hey, we might not be able to do *that*, but along
those lines, we might be able to do *this*...", and viola! (or cello, or
some other stringed instrument...)
