[opensource-dev] Fixing the Assets
Dzonatas Sol
dzonatas at gmail.com
Fri Aug 6 14:28:21 PDT 2010
Here is the proposal, as a routine. The written logical explanation in
English with normalized words defeats the purpose of the routine for
every reason that supports it.
"Got to put a face on it:"
Store timestamp by UUID.
Keep secondary UUID to XOR with every second.
Doesn't matter if timestamp of UUID changes within that second, as long
as one of the two changes.
That's a new "second".
Do that again for the new "minute" based on 60 new seconds.
The hour is optional, as there are several more value to consider to
make a new "hour".
And so on, until you have decided on a new "timestamped UUID".
Store the original assets by Asset UUID or new timestamped UUID.
Don't transmit the original timestamp of the asset... only transmit the
the newer created unique value.
The client-side can then create assets by that newer value, which would
then create its own timestamp on the client side.
I think LL can figure out the rest...
Save yourself!
--
--- https://twitter.com/Dzonatas_Sol ---
Web Development, Software Engineering, Virtual Reality, Consultant
More information about the opensource-dev
mailing list