[Mono-bugs] [Bug 74279][Wis] Changed - XML parsing Bug in MiniParser

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Mon, 4 Apr 2005 09:18:30 -0400 (EDT)

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by sebastien@ximian.com.


--- shadow/74279	2005-04-03 19:00:34.000000000 -0400
+++ shadow/74279.tmp.24214	2005-04-04 09:18:30.000000000 -0400
@@ -1,22 +1,21 @@
 Bug#: 74279
 Product: Mono: Class Libraries
 Version: 1.1
 OS: unknown
 OS Details: 
-Status: NEW   
+Status: NEEDINFO   
 Severity: Unknown
 Priority: Wishlist
 Component: Mono.Security
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: gnauck@ag-software.de               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
 Summary: XML parsing Bug in MiniParser
 Please fill in this template when reporting a bug, unless you know what 
 you are doing.
 Description of Problem:
@@ -101,6 +100,40 @@
 ------- Additional Comments From atsushi@ximian.com  2005-04-03 19:00 -------
 ah, ok I got it. Well, it is an intended design. There used to be
 similar report. My best descriptive answer is here:
+------- Additional Comments From sebastien@ximian.com  2005-04-04 09:18 -------
+Try to see if the problem is in MiniParser or SecurityParser. The
+design of MiniParser was to allow people to easily write their own
+specific parser on top of it (as simple or complex they wishes). My
+hack, the SecurityParser, made it a more "general" parser but
+(probably) loose a lot of original flexibility in doing so.
+Anyway the whole idea of writing SecurityParser was to produce
+SecurityElement from a string - which was something not possible with
+the framework prior to 2.0. The security permissions and the key
+persistance are the only features requiring the SecurityParser and
+both have _very_ simple XML data to deal with.
+So either the problem is:
+* in MiniParser; or
+* in SecurityParser;
+* affects; or
+* doesn't affects; 
+the SecurityElement.FromString (available in 2.0). 
+The later being the most serious (but not immediate) issue.
+If it doesn't affect 2.0 then I don't think we want to put much effort
+into fixing this, but I would gladly accept patch in Mono.Security.dll
+to make it better. In this case it may not be worth to fix
+SecurityParser (if the problem is located there) but to write a new,
+more complete (general or specific), parser on top of MiniParser.
+Finally keep in mind the "mini" of the parser. Huge patches or changes
+for stuff rarely required XML functionalities are likely to be ignored
+as we already have a much better alternative for them.