Splitting Network.URI from the network package

[Carter Schonwald]

+1 to this. Evolving the lib to support text too would be high roi.

I'd be happy to help maintain URI if that sort of change / evolution was in
scope for how to evolve it.

On Friday, August 15, 2014, Herbert Valerio Riedel <hvr at gnu.org> wrote:

> On 2014-08-15 at 10:35:54 +0200, Christian Maeder wrote:
>
> [...]
>
> > network-uri should be preferred over other "uri" packages [1]
>
> Tbh, I don't like the current Network.URI API, as it's heavily 'String'
> based. If you have process/store a lot of URIs you incur a measurable
> overhead.
>
> Fwiw, this has been noticed in the past:
>
>  - http://www.haskell.org/pipermail/haskell-cafe/2012-March/100004.html
>
>  - http://permalink.gmane.org/gmane.comp.lang.haskell.libraries/18761
>
>
> However, I am not aware of any Network.URI replacement based on 'Text'
> or 'ByteString' yet. So far I've just coded up minimal URL parsers that
> worked on a small subset of the URI grammer when I wanted something more
> efficient.
>
> Cheers,
>   hvr
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org <javascript:;>
> http://www.haskell.org/mailman/listinfo/libraries
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/libraries/attachments/20140815/06c8babe/attachment.html>