On Wed, Dec 1, 2010 at 4:06 PM, Marco Trevisan (Treviño) <m...@3v1n0.net> wrote: > > I've also another version for this function, this one supports any > protocol, following the syntax rules stated by the RFC 3986 considering > everything that precedes a semicolon (:) as the schema, and the rest as > the path (this allows to get working about:* pages too, also if > webkit-efl doesn't seem to support them yet). However I had to check > that the "parsed" schema was not actually a port number or a password > (with urls like www.google.com:80 or http://user:p...@anysite.com:80 ;) > > All the cases I've tested seem to work, let me know what you think. >
I've checked RFC 3896 and it seems that URL parsing isn't as simple as it sounds. There are libraries there to provide URL parsing and they're quite complicated because there are lots of ambiguities and other pitfalls. I don't see any need right now to make this thing beefier, since the current naive implementation is working fine already. Well, except for "about:" URLs, but I think this is the wrong layer to put this; there is already a patch to WebKit Soup backend to support custom scheme handlers, which will also make it possible to embed external resources (e.g. images). -- Cheers, Leandro ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
