[ 
https://issues.apache.org/jira/browse/RIVER-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Firmstone resolved RIVER-386.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: River_3.0.0

Outrigger refactored to use java concurrency files, FastList removed

> Refactor of FastList inside of Outrigger
> ----------------------------------------
>
>                 Key: RIVER-386
>                 URL: https://issues.apache.org/jira/browse/RIVER-386
>             Project: River
>          Issue Type: Improvement
>          Components: com_sun_jini_outrigger
>            Reporter: Tom Hobbs
>             Fix For: River_3.0.0
>
>
> There is talk on the mailing list of refactoring the internals of Outrigger, 
> with particular attention being paid to FastList.
> See mail archive:
> http://mail-archives.apache.org/mod_mbox/incubator-river-dev/201012.mbox/%[email protected]%3e
> There are many considerations which need to be taken, not least of all is the 
> scalability and performance requirements of some users of outrigger.  There's 
> also experiments which could be interesting in swapping the back-end of 
> Outrigger for a relational database of some description - that's probably a 
> separate JIRA though.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to