On Wed, Aug 9, 2017 at 12:41 PM, Oleg Kalnichevski <ol...@apache.org> wrote:

> Folks
> I just committed a large chunk of code with the last big feature I had
> in mind for the HttpCore 5.0 release. The server side transports (both
> classic and async) now provide filter support that can be used to
> implement cross-cutting aspects for all incoming requests such the
> expect-continue handshake or user authentication and authorization.
> https://github.com/apache/httpcomponents-core/blob/master/httpcore5-tes
> ting/src/test/java/org/apache/hc/core5/testing/classic/ClassicAuthentic
> ationTest.java
> https://github.com/apache/httpcomponents-core/blob/master/httpcore5-tes
> ting/src/test/java/org/apache/hc/core5/testing/nio/Http1AuthenticationT
> est.java
> Now I would like to shift the focus of development efforts from adding
> new features and making disruptive API changes to code stabilization,
> API polish and test coverage improvement. I
> _IMPORTANT_: if you would like to make some big API changes: move code
> around, rename packages and classes, introduce new naming conventions,
> propose new features with a large API footprint _NOW_ would be a good
> time to do so.
> @Gary
> You wanted to discuss naming conventions some while ago, did not you?

Maybe so but I do not recall ATM. I might have to dig through the archives
when I have some free time.

> It is probably also the right time to discuss whether or not we should
> consider building a full featured HTTP server with statement management
> (server side cookies), authentication (server side auth schemes),
> pluggable user registries, and all those things that used to be out of
> project scope.

Over that last few months, my focus has been on building a custom
proprietary proxy on top of HttpCore 4.

I've been telling myself that I should port it to Core 5 but it has felt a
little too soon, as I've seen a lot of code moving around there. It sounds
like the code should be more stable.

What I am looking at now, are some missing building blocks. For example, I
want to support the HTTP headers Via and Forwarded but there is no
HttpRequestInterceptor for these. I plan on writing those and if these are
plain enough, I would like to add them to Core 4 and 5.

> I would like to cut another, likely last, ALPHA release soon and
> propose moving to the BETA phase.

Great, I'm all for more Alpha and Beta releases.


> Oleg
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
> For additional commands, e-mail: dev-h...@hc.apache.org

Reply via email to