Ticket #64 (new task)

Opened 4 years ago

Last modified 2 years ago

Reconsider equality in XMLMap

Reported by: clange Owned by: vzholudev
Priority: major Milestone: zzz Future zzz
Component: [SI] NTN Version:
Keywords: Cc: nmueller, cmueller, dmisev
Blocked By: Blocking:
Due to close: Include in GanttChart: no
Dependencies: Due to assign:

Description

Comment moved from the source of XMLMap:

Is the current equality the kind of equality we want? Or should we instead consider the equality given by the pattern matching algorithm of ntn.rnd.Pattern? Comparing two XML elements is like pattern matching without placeholders -- we should either obtain an exception (unequal) or some non-null Matcher (equal). But note that we'd need to replace all placeholders by something "constant", e.g. om:OMVs with special names, as one cannot "match" a placeholder against a placeholder.
-- Christoph, 2008/01/25 (summarizing discussion with Normen)

Change History

Changed 4 years ago by clange

Citing a comment given by Dimitar:

I'm not sure if your comment in XMLMap is even possible to do, at least from performance point of view. That XMLMap is heavily used, and I even had to disable the XML diff there (the USE_XML_EQUALITY flag is false by default), because it was increasing the total running time for some 90%, and I'd rather allow a couple of duplicate entries than wait 10s for adding the simplest notation file. So I'm just guessing that doing sth like pattern matching there would make a lot more than 90%.

Changed 4 years ago by nmueller

  • due_assign YYYY/MM/DD deleted
  • component changed from unknown to [SI] NTN
  • due_close YYYY/MM/DD deleted
  • milestone set to zzz Future zzz

Changed 2 years ago by nmueller

  • owner changed from nmueller to vzholudev
Note: See TracTickets for help on using tickets.