[
http://jira.amdatu.org/jira/browse/AMDATU-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10427#comment-10427
]
Bram de Kruijff commented on AMDATU-190:
----------------------------------------
Committed some proof of concept code based on Commons HttpClient 4.1 with
caching support in r452
> 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.
> 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?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
