On 2010-12-27 21.35, Niclas Hedhman wrote:
Uhhh... Isn't the 'burden of guilt' wrongly put here?
The burden of guilt is always the same, i.e. on the one proposing that "what is in Qi4j now is not enough, because I need to do X, and am considering to do Y". You still have not really presented exactly why UUID's is a problem. I can guess, but it would be better if you spelled it out, so it is clear.
In my own case, clients always do lookups based on following links in a REST API, so the id's are opaque. There is little point in having a structure in the id itself if that is the case. The only reason I can think of, for architectural reasons, is if you want to do sharding and hence simplify routing to the correct server.
So I'm guessing there's some other problem, that is yet to be spelled out, that you're facing. Exactly what is it?
/Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
