On Fri, Apr 5, 2013 at 8:01 AM, Pierre Joye <pierre....@gmail.com> wrote:
> On Thu, Apr 4, 2013 at 9:52 PM, Hannes Magnusson
> <hannes.magnus...@gmail.com> wrote:
>
> > Its not only about maintaining it.
> > This experiment failed a long time ago. Overwriting the core streams
> > has proven itself to be the wrong way.
>
> I cannot agree more.
>
> > If there was a way for userspace to say "overload with curl" then thats
> fine.
> > We already have a procedure for this:
> >
> > stream_wrapper_unregister("http");
> > stream_wrapper_register("http", "CurlStreamWrapper");
> > and then stream_wrapper_restore("http") to go back to the core streams.
> >
>
> I wonder what one will do with open streams during the switches. That
> can't go well.
>
Hey, that's true, we may meet strange behavior.
I would say, why not create a new wrapper protocol, aka "curl://".
I know it is more ugly than "http://"; , but "curl://" solves the problem
doesn't it ?
I wonder how we could use curl other protocols than http using curl://
though :p
Julien.P
