Re: [vfs] new http4 provider, not replace http?

2019-10-23 Thread Woonsan Ko
> > > e...@zusammenkunft.net> wrote: > > > > > > > > >> Hello, > > > > > > > > >> > > > > > > > > >> I am for http4. In the begining it wont be maped in the > > > > > > > S

Re: [vfs] new http4 provider, not replace http?

2019-01-01 Thread Woonsan Ko
> > > > > Sounds good to me. > > > > > > > > > > > > > > > >> > > > > > > > >> I do wonder if we can get rid of a Special https Provider and > > have > > > > > > only one (http4) which can handle both Ki

Re: [vfs] new http4 provider, not replace http?

2018-11-03 Thread Gary Gregory
> what > > > > > do you think? > > > > > > > From user's perspective, it seems better to keep 'https' > separately > > > > > > > from 'http'. 'http4s' and 'http4' accordingly. > > > > > > > We can possibly consider ne

Re: [vfs] new http4 provider, not replace http?

2018-11-02 Thread Woonsan Ko
.html' (equivalent to the > > first) or > > > > > > 'http4:https://www.example.com/index.html. But that doesn't seem > > to > > > > > > make anything more convenient than simply allowing either > > > > > > 'http4://www.example.com/ind

Re: [vfs] new http4 provider, not replace http?

2018-11-02 Thread Gary Gregory
m/index.html' or > > > > > 'http4s://www.example.com/index.html'. > > > > > So, I'm personally inclined to keep the existing pattern to have > > > > > separate providers. > > > > > > > > > >> > > > > >>

Re: [vfs] new http4 provider, not replace http?

2018-11-02 Thread Woonsan Ko
le.com/index.html' or > > > > 'http4s://www.example.com/index.html'. > > > > So, I'm personally inclined to keep the existing pattern to have > > > > separate providers. > > > > > > > >> > > > >> Besides that, I wonder if we also (on

Re: [vfs] new http4 provider, not replace http?

2018-11-01 Thread Gary Gregory
> > with HttpComponents HttpClient v4 first. ;-) Also, it's very matured > > > and well-accepted, comparing with the new JDK HttpClient. > > > I'm open to a possibility in the near future for a new separate > > > provider, possibly called 'jdkhttp' with JDK HttpClient mod

Re: [vfs] new http4 provider, not replace http?

2018-10-31 Thread Woonsan Ko
very matured > > and well-accepted, comparing with the new JDK HttpClient. > > I'm open to a possibility in the near future for a new separate > > provider, possibly called 'jdkhttp' with JDK HttpClient module. > > > > Kind regards, > > > > Woonsan >

Re: [vfs] new http4 provider, not replace http?

2018-08-15 Thread Woonsan Ko
pen to a possibility in the near future for a new separate > provider, possibly called 'jdkhttp' with JDK HttpClient module. > > Kind regards, > > Woonsan > >> >> Gruss >> Bernd >> >> -- >> http://bernd.eckenfels.net >> >> Von:

Re: [vfs] new http4 provider, not replace http?

2018-08-08 Thread Woonsan Ko
. Kind regards, Woonsan > > Gruss > Bernd > > -- > http://bernd.eckenfels.net > > Von: Woonsan Ko > Gesendet: Mittwoch, 8. August 2018 18:35 > An: Commons Developers List > Betreff: [vfs] new http4 provider, not replace http? > > Hi, > > I'm tryin

Re: [vfs] new http4 provider, not replace http?

2018-08-08 Thread Bernd Eckenfels
also (only?) should consider the new JDK httpclient api? Gruss Bernd -- http://bernd.eckenfels.net Von: Woonsan Ko Gesendet: Mittwoch, 8. August 2018 18:35 An: Commons Developers List Betreff: [vfs] new http4 provider, not replace http? Hi, I'm trying to contribute for VFS-360. What a nice

[vfs] new http4 provider, not replace http?

2018-08-08 Thread Woonsan Ko
Hi, I'm trying to contribute for VFS-360. What a nice ticket number! After a brief look, I'm considering to add a new provider in a separate package, 'http4' (based on HttpComponents HttpClient), keeping the old one, 'http' (based on the old Commons HttpClient), as-is. The reason is that I don't