Remove redundant Shindig extender filter registration
-----------------------------------------------------
Key: AMDATU-335
URL: http://jira.amdatu.org/jira/browse/AMDATU-335
Project: Amdatu
Issue Type: Improvement
Components: Amdatu OpenSocial
Affects Versions: 0.2.0
Reporter: Bram de Kruijff
At present the Open Social subproject always registers two Dispatcher extender
filters that do exactly the same thing (storing resolved tenant on
threadlocal). Only noticeable difference is a difference pattern. This is at
least suboptimal with regard to performance as mosts many will hit both
org.amdatu.opensocial.profile.service.TenantHostnameDispatchExtenderFilter
at (/gadgets/.*)|(/social/rest/.*)
org.amdatu.opensocial.shindig.service.TenantHostnameDispatchExtenderFilter at
.*
This construct seems to be motivated that in theory (not implementation) the
profile service could be deployed without shindig. On the other hand there are
(or could be?) more openSocial services requiring this threadlocal hack which
is why shindig also performs the magic.
Anyhow, it should be either consolidated to one filter registration , probably
in shindig if we can consider is subproject to be one composite or a seperate
deployment unit required once.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
