- From: Jonas Sicking <jonas@sicking.cc>
- Date: Sat, 13 Nov 2010 00:33:06 -0800
- To: Keean Schupke <keean@fry-it.com>
- Cc: Jeremy Orlow <jorlow@chromium.org>, "Tab Atkins Jr." <jackalmage@gmail.com>, Pablo Castro <Pablo.Castro@microsoft.com>, "public-webapps@w3.org" <public-webapps@w3.org>
On Fri, Nov 12, 2010 at 11:59 PM, Keean Schupke <keean@fry-it.com> wrote: > Why not return the full 64bit ID in an opaque object? Maths and comparing > IDs is meaningless anyway. Then we'd have to overload both the structured clone algorithm and the == javascript operator. Even with 53 bits you can generate a new ID a million times a second for 285 years. So I really don't think we need to worry. And if anyone is still worrying then I'd say lets look at this in a hundred years or so, at which point I suspect that javascript has grown support for 64bit integers bringing us back to that half a million year limit :) / Jonas
Received on Saturday, 13 November 2010 08:34:00 UTC