[
http://jira.amdatu.org/jira/browse/AMDATU-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bram de Kruijff updated AMDATU-190:
-----------------------------------
Description:
Following up on the discussion around AMDATU-82 I'd like to suggest a new
subproject thath provides HTTP cache/proxy functionality. As many Amdatu
services will deal with HTTP it services a generic HTTP cache mechanism will
void the need for add hoc non policy caches, provide a very (re)usable
foundation service and (if used) provide a centralized manageable component in
charge of HTTP connections as opposed to point-to-point connections all over
the codebase.
I think as a rule this kind of subproject, having a clear enduser business
interface, should prove itself by delivering not only a service, useable to a
developer, but also an out of the box working solution, It should be possible
to release/provision an "Amdatu HttpProxy server" that can be used as a
(reverse) (caching) proxy and possible (managed) loadbalancer. The latter might
be of interest when we move to clustered deployments.
Mental notes:
1) Support concurrent access / manage connections
2) Encapsulate HTTP caching policies
3) Handle storage and garbage collection
4) Expose through well know (httpclient / java net) service API
5) Expose through REST API and/or as proxy
6) Seems like HTTPClient is adding some kind of support in 4.1
(https://issues.apache.org/jira/browse/HTTPCLIENT-427)
7) Transparently handle/add GZIP support.
8) Managed loadbalancing(?)
Questions:
1) Any other suggestions on an existing library that would help us out?
was:
Following up on the discussion around AMDATU-82 I'd like to suggest a new
subproject thath provides HTTP cache/proxy functionality. As many Amdatu
services will deal with HTTP it services a generic HTTP cache mechanism will
void the need for add hoc non policy caches, provide a very (re)usable
foundation service and (if used) provide a centralized manageable component in
charge of HTTP connections as opposed to point-to-point connections all over
the codebase.
Thoughts:
1) Support concurrent access / manage connections
2) Encapsulate HTTP caching policies
3) Handle storage and garbage collection
4) Expose through well know (httpclient / java net) service API
5) Expose through REST API and/or as proxy
6) Seems like HTTPClient is adding some kind of support in 4.1
(https://issues.apache.org/jira/browse/HTTPCLIENT-427)
Questions:
1) Any other suggestions on an existing library that would help us out?
> Introduce amdatu http cache/proxy subproject
> --------------------------------------------
>
> Key: AMDATU-190
> URL: http://jira.amdatu.org/jira/browse/AMDATU-190
> Project: Amdatu
> Issue Type: New Feature
> Environment: any
> Reporter: Bram de Kruijff
> Assignee: Bram de Kruijff
> Priority: Minor
>
> Following up on the discussion around AMDATU-82 I'd like to suggest a new
> subproject thath provides HTTP cache/proxy functionality. As many Amdatu
> services will deal with HTTP it services a generic HTTP cache mechanism will
> void the need for add hoc non policy caches, provide a very (re)usable
> foundation service and (if used) provide a centralized manageable component
> in charge of HTTP connections as opposed to point-to-point connections all
> over the codebase.
> I think as a rule this kind of subproject, having a clear enduser business
> interface, should prove itself by delivering not only a service, useable to a
> developer, but also an out of the box working solution, It should be possible
> to release/provision an "Amdatu HttpProxy server" that can be used as a
> (reverse) (caching) proxy and possible (managed) loadbalancer. The latter
> might be of interest when we move to clustered deployments.
> Mental notes:
> 1) Support concurrent access / manage connections
> 2) Encapsulate HTTP caching policies
> 3) Handle storage and garbage collection
> 4) Expose through well know (httpclient / java net) service API
> 5) Expose through REST API and/or as proxy
> 6) Seems like HTTPClient is adding some kind of support in 4.1
> (https://issues.apache.org/jira/browse/HTTPCLIENT-427)
> 7) Transparently handle/add GZIP support.
> 8) Managed loadbalancing(?)
> Questions:
> 1) Any other suggestions on an existing library that would help us out?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
