[Mono-dev] Custom Uri Parsing
alan.mcgovern at gmail.com
Thu Feb 11 18:45:03 EST 2010
The main reason why I didn't actually do any work on this at the time is
that it would probably take 1 man month to do the rewrite, pass the existing
tests and write more tests for the new behaviours and I didn't have a month
free to do it ;) Proper support for the new parser API is required to
properly support System.IO.Packaging, so I'd be willing to offer any advice
if you want to take on the task.
The biggest problem (as I saw it at the time) is that this is an all or
nothing kind of patch. It might be impossible to do this one uri scheme at a
time without making things ridiculously complicated internally. While the
existing code will be useful as a guide, you will end up chopping it up into
tiny pieces and moving it around into the different parser subclasses.
p.s. The above should be mostly accurate, but the last time I looked at this
was when I sent the original email ;)
On Thu, Feb 11, 2010 at 5:09 AM, Miguel de Icaza <miguel at novell.com> wrote:
> Some searching also threw up this post to the list back in October 2008:
> . I’ve looked in to the Mono implementation in svn, and it still appears
> that most of the Uri class decodes specific Uri content itself rather than
> delegating to Uri parsers.
> I do not believe we ever moved to that scheme of Uri parsing.
> I was wondering if anyone knew if the post above was ever followed up, or
> whether the suggestion wasn’t implemented for some reason? I guess this
> should probably be filed as a bug, as the functionality was added in .NET 2?
> If you’d welcome a patch I could probably submit something based on Alan’s
> I would love to see a patch based on Alan's patch.
> It should be simpler these days since Mono trunk has dropped support for
> 1.0 compatibility
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list