You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Kevin Brown (JIRA)" <ji...@apache.org> on 2008/06/09 10:09:45 UTC
[jira] Commented: (SHINDIG-279) Configurable and clusterable cache
for Gadgets server
[ https://issues.apache.org/jira/browse/SHINDIG-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603506#action_12603506 ]
Kevin Brown commented on SHINDIG-279:
-------------------------------------
Sorry for the late follow up on this one. You've done great work Ian -- thank you.
Does anyone have a strong opinion one way or another here? Perhaps we could make separate artifacts for each of these and extract out the caching-related parts of the Guice module to simplify integration and let people choose which option to go with?
> Configurable and clusterable cache for Gadgets server
> -----------------------------------------------------
>
> Key: SHINDIG-279
> URL: https://issues.apache.org/jira/browse/SHINDIG-279
> Project: Shindig
> Issue Type: Improvement
> Components: Gadget Rendering Server (Java)
> Reporter: Ian Boston
> Attachments: SHINDIG-279-jcs.patch, SHINDIG-279.patch
>
>
> If the the Gadgets server is going to perform caching, then a configurable cache that has all the features that you might expect in production. Attached is a patch to put ehcache behind the Cache interface and introduce a ShindigCacheManager, that registers with JMX for statistics and management.
> The patch is fully integrated into the gadgets server guice config, with tests for each class. It also appears to startup Ok.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.