I'm curious, and this would help me understand gnx's: This sounds like Leo currently parses gnx's. For what purpose(s)? I thought Leo already worked the way Ville is proposing, that Leo just "knew" a gnx would be unique, without caring what it looked like in terms of structure (date/time stamp, user id, etc.). On Apr 12, 2011 9:10 AM, "Ville M. Vainio" <[email protected]> wrote: > On Tue, Apr 12, 2011 at 5:45 PM, Edward K. Ream <[email protected]> wrote: > >> That would utterly defeat the one and only purpose of gnx's, namely a >> guaranteed unique, immutable identity for every Leo node. >> >> We can not possibly allow this: it would surely corrupt Leo data. > > It would only corrupt data if a plugin developer screws up by reusing old gnx's. > > Leo itself would still assign the same kind of gnx's, what we want is > to ensure leo doesn't crash if gnx format changes. Let's say a plugin > wants to use 128 bit GUUID gnx - it should not crash leo, even if it > can't be parsed with current gnx parsing rules. > > That is, IMO leo should have no business ever parsing the gnx anyway. > It should generate the gnx, and then ignore how it was generated. > > -- > You received this message because you are subscribed to the Google Groups "leo-editor" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to [email protected]. > For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en. >
-- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
