You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by Oleg Kalnichevski <ol...@apache.org> on 2007/04/06 21:29:47 UTC
[HttpCore] tasks blocking HttpCore API freeze
Folks,
Here is the list of my ideas in a random order of what needs to be done
for the next release of HttpCore
(1) Reverse proxy sample based on HttpCore NIO. This is needed to make
sure we the NIO API is fully adequate for such a job.
(2) HTTPCORE-63. I hope Anders can see this one to a logical conclusion.
Otherwise I'll take it over.
https://issues.apache.org/jira/browse/HTTPCORE-63
(3) HTTPCORE-64. We have lots of places where HttpParams and HttpContext
are being used. We need to make sure the use of these interfaces is
consistent across the entire HttpCore
https://issues.apache.org/jira/browse/HTTPCORE-64
(4) HTTPCORE-43. This feature is expected to improve performance of file
bound operations and does not seem like a lot of work
https://issues.apache.org/jira/browse/HTTPCORE-43
(5) HTTPCORE-48. I think this one can be dealt with during the BETA
development phase. Does not seem to entail any API changes. Nice to have
but not a must. I am going to target it for BETA-1 if hear no
objections
https://issues.apache.org/jira/browse/HTTPCORE-48
(6) HTTPCORE-21. Something I personally could live without
https://issues.apache.org/jira/browse/HTTPCORE-21
(7) I would like to decouple the HTTP message parsing code from HTTP
connection objects. Not sure this is doable / worth the trouble.
(8) Provide test coverage for ThrottlingHttpServiceHandler. Develop its
client side counterpart.
As far as I can tell these tasks need to be tackled before we can
consider freezing the API and moving to the BETA development phase.
Have I missed anything? Thoughts?
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org
RE: [HttpCore] tasks blocking HttpCore API freeze
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Fri, 2007-04-06 at 13:14 -0700, Anders Wallgren wrote:
> I'll take responsibility for finishing the patch for HTTPCORE-63. It's
> not much work, but is there a rough timeline you're working with for the
> next release, so I can figure out where to slot it in?
>
> anders
>
Hi Anders,
It will probably take me 4 to 5 months to complete these tasks if I work
on them alone. HTTPCORE-63 is not blocking any other item so there is
really no rush. Besides, do not feel obliged. Feel free to work on it if
you think contributing code to ASF is a good thing and learning the way
patch submission process works may be something useful for you.
Cheers
Oleg
> -----Original Message-----
> From: Oleg Kalnichevski [mailto:olegk@apache.org]
> Sent: Friday, April 06, 2007 12:30 PM
> To: HttpComponents Project
> Subject: [HttpCore] tasks blocking HttpCore API freeze
>
> Folks,
>
> Here is the list of my ideas in a random order of what needs to be done
> for the next release of HttpCore
>
> (1) Reverse proxy sample based on HttpCore NIO. This is needed to make
> sure we the NIO API is fully adequate for such a job.
>
> (2) HTTPCORE-63. I hope Anders can see this one to a logical conclusion.
> Otherwise I'll take it over.
> https://issues.apache.org/jira/browse/HTTPCORE-63
>
> (3) HTTPCORE-64. We have lots of places where HttpParams and HttpContext
> are being used. We need to make sure the use of these interfaces is
> consistent across the entire HttpCore
> https://issues.apache.org/jira/browse/HTTPCORE-64
>
> (4) HTTPCORE-43. This feature is expected to improve performance of file
> bound operations and does not seem like a lot of work
> https://issues.apache.org/jira/browse/HTTPCORE-43
>
> (5) HTTPCORE-48. I think this one can be dealt with during the BETA
> development phase. Does not seem to entail any API changes. Nice to have
> but not a must. I am going to target it for BETA-1 if hear no
> objections
> https://issues.apache.org/jira/browse/HTTPCORE-48
>
> (6) HTTPCORE-21. Something I personally could live without
> https://issues.apache.org/jira/browse/HTTPCORE-21
>
> (7) I would like to decouple the HTTP message parsing code from HTTP
> connection objects. Not sure this is doable / worth the trouble.
>
> (8) Provide test coverage for ThrottlingHttpServiceHandler. Develop its
> client side counterpart.
>
> As far as I can tell these tasks need to be tackled before we can
> consider freezing the API and moving to the BETA development phase.
>
> Have I missed anything? Thoughts?
>
> Oleg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> httpcomponents-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> httpcomponents-dev-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org
RE: [HttpCore] tasks blocking HttpCore API freeze
Posted by Anders Wallgren <an...@electric-cloud.com>.
I'll take responsibility for finishing the patch for HTTPCORE-63. It's
not much work, but is there a rough timeline you're working with for the
next release, so I can figure out where to slot it in?
anders
-----Original Message-----
From: Oleg Kalnichevski [mailto:olegk@apache.org]
Sent: Friday, April 06, 2007 12:30 PM
To: HttpComponents Project
Subject: [HttpCore] tasks blocking HttpCore API freeze
Folks,
Here is the list of my ideas in a random order of what needs to be done
for the next release of HttpCore
(1) Reverse proxy sample based on HttpCore NIO. This is needed to make
sure we the NIO API is fully adequate for such a job.
(2) HTTPCORE-63. I hope Anders can see this one to a logical conclusion.
Otherwise I'll take it over.
https://issues.apache.org/jira/browse/HTTPCORE-63
(3) HTTPCORE-64. We have lots of places where HttpParams and HttpContext
are being used. We need to make sure the use of these interfaces is
consistent across the entire HttpCore
https://issues.apache.org/jira/browse/HTTPCORE-64
(4) HTTPCORE-43. This feature is expected to improve performance of file
bound operations and does not seem like a lot of work
https://issues.apache.org/jira/browse/HTTPCORE-43
(5) HTTPCORE-48. I think this one can be dealt with during the BETA
development phase. Does not seem to entail any API changes. Nice to have
but not a must. I am going to target it for BETA-1 if hear no
objections
https://issues.apache.org/jira/browse/HTTPCORE-48
(6) HTTPCORE-21. Something I personally could live without
https://issues.apache.org/jira/browse/HTTPCORE-21
(7) I would like to decouple the HTTP message parsing code from HTTP
connection objects. Not sure this is doable / worth the trouble.
(8) Provide test coverage for ThrottlingHttpServiceHandler. Develop its
client side counterpart.
As far as I can tell these tasks need to be tackled before we can
consider freezing the API and moving to the BETA development phase.
Have I missed anything? Thoughts?
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail:
httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail:
httpcomponents-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org