On Thu, Mar 26, 2009 at 11:22 AM, Brett Wilson <[email protected]> wrote: > Those are exposed, but I wonder which cases an extension needs to > refer to them. They are internal IDs generated by sqlite. If you clear > your history, you'll get re-used ones. This could also theoretically > possible happen if you delete a single item, but I don't know if this > happens in practice. So they are often persistent, but the way you ask > makes me nervous.
I'm thinking of a use case where somebody wanted to synchronize browser history between machines. It would be more convenient to do this if there was a unique client side ID that didn't change for each visit. I admit this is probably a far-out use case, but I figured if it was easy to enable, we might as well. - a --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
