The reason I put the annotation data in the same file is for ease of management of the files (eg. attaching trace file to the JIRA issue, sending it in email, or however other way they get used). This way the information is self-contained and you'll never run into a situation where the annotation file is lost, mixed up with a different trace file, ... It just easier to manage.
Having said that, the down said is as you said. The original file is not pure log data after annotations are stored. It is easy to remove the annotations from the log file, but then you loose the annotations. If the log files are often processed by other programs after sipviewer adds annotations then perhaps it would be worth separating the two. I don't know the frequency of how often that happens and which of the two benefits people would rather have. Easy to manage files, or pure log files. If the consensus is to change it I can do that. Tom > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Worley, Dale AVAYA (BL60:9D30) > Sent: Wednesday, December 23, 2009 3:33 PM > To: Lawrence, Scott AVAYA (BL60:9D30) > Cc: sipX-dev > Subject: Re: [sipX-dev] sipviewer display configuration annotations > > On Wed, 2009-12-23 at 15:16 -0500, Scott Lawrence wrote: > > On Wed, 2009-12-23 at 14:48 -0500, Dale Worley wrote: > > > In regard to having sipviewer apply annotations to the > siptrace file > > > to show how the file should be displayed: The annotations should > > > have their own XML namespace, so the annotations can be cleanly > > > separated from the trace data itself. > > > > What's wrong with just different element names? > > It would work. But the display annotations are distinctly > different semantically. Putting them in a separate namespace > would clarify the distinction, and maintain separation of > concerns between the programs that extract and process > traces, and sipviewer. > > Dale > > > _______________________________________________ > sipx-dev mailing list [email protected] List > Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > sipXecs IP PBX -- http://www.sipfoundry.org/ > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
