Am 2015-11-20 um 16:33 schrieb Oleg Kalnichevski:
On Fri, 2015-11-20 at 15:13 +0100, Michael Osipov wrote:
On Fri, 2015-11-20 at 12:42 +0100, Michael Osipov wrote:
On Thu, 2015-11-19 at 23:27 +0000, sebb wrote:
On 19 November 2015 at 21:17, Michael Osipov <micha...@apache.org> wrote:
Am 2015-11-19 um 12:32 schrieb Oleg Kalnichevski:
...
Would this be all right for everyone?
org.apache.hc.core5.http
Why do you want to use the redundant 'http'?
While not very likely we might have non HTTP protocol support as well,
such as Websockets.
I see but WebSockets share no common code with HTTP except the initial
handshake.
I would rather see this as another top level project because HttpClient's API is
highly optimized for HTTP and not a general-purpose one like Commons VFS.
Project charter allows us to pursue development of a component toolset
'focused on HTTP and associated protocols'.
I wouldn't really say that WebSockets are an associated protocol due to
its different nature in communication and messaging.
I highly doubt that we well gain the proper momentum to develop
something for WebSockets. It should be at least as good as Jetty's WS
Client API.
I also can well imagine SSL related components being in a separate
namespace like 'org.apache.hc.core5.ssl'
That would be ok.
At the end, you propose:
HC Core: org.apache.hc.http.core5
HC Client: org.apache.hc.http.client5
HC Async Cilent: org.apache.hc.http.asyncclient5
Is that right?
I have intentionally switched that because client wouldn't live under
core5. I have already Java modules in mind Oracle is about to introduce
in Java 9 (auto module feature).
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
