[
https://issues.apache.org/jira/browse/BLUR-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikrant Navalgund updated BLUR-183:
-----------------------------------
Attachment: BLUR-183-MASTER-v2.patch
Hi Aaron,
I looked into the issue of initializing the BlurConfiguration obj. Based on the
following points it looks like its complex or unnecessary. Correct me if i am
wrong.
1. BlurClientManager statically initializes the ClientPool.
2. BlurConfiguration throws an IOException, so I need to catch it in
BlurClientManager or ClientPool.
3. The logical place to initialize the ClientPool would be in
BlurClientManager, which I need to do in the static block of BlurClientManager
again.
So, to make the soln simple I am doing it in the ClientPool.
Please let me know if I am missing something.
Also, i have attached an updated patch which has a small change from the
previous version.
Regards,
Vikrant
> Auto disconnect clients that have been idle for a period of time
> ----------------------------------------------------------------
>
> Key: BLUR-183
> URL: https://issues.apache.org/jira/browse/BLUR-183
> Project: Apache Blur
> Issue Type: Improvement
> Components: Blur
> Affects Versions: 0.2.0, 0.3.0
> Reporter: Aaron McCurry
> Fix For: 0.3.0
>
> Attachments: BLUR-183-MASTER.patch, BLUR-183-MASTER-v2.patch
>
>
> In the BlurClientManger, automatically disconnect client connections when
> they have not been used in a certain amount of time.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
