You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Hasan Ceylan (JIRA)" <ji...@apache.org> on 2011/08/17 20:36:29 UTC
[jira] [Updated] (SHINDIG-1581) When default-forced-libs and
externalize-feature-libs, feature resources are duplicated.
[ https://issues.apache.org/jira/browse/SHINDIG-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hasan Ceylan updated SHINDIG-1581:
----------------------------------
Attachment: SHINDIG-1581.patch
Proposed fix for the issue
> When default-forced-libs and externalize-feature-libs, feature resources are duplicated.
> ----------------------------------------------------------------------------------------
>
> Key: SHINDIG-1581
> URL: https://issues.apache.org/jira/browse/SHINDIG-1581
> Project: Shindig
> Issue Type: Bug
> Components: Java
> Affects Versions: 2.0.2
> Reporter: Hasan Ceylan
> Priority: Blocker
> Attachments: SHINDIG-1581.patch
>
>
> For network performance we choose to set externalize-feature-libs to true to lower ifr response sizes. On the other hand we also have some default-forced-libs.
> We have discovered that in this case the external script tag inserted two times one for the default-forced-libs, other for the gadget features. With JS servlet being unaware of there are two separate requests, the transitive dependencies included twice, as a result of this, some of the core libraries included twice.
> This behavior can be tested with setting externalize-feature-libs to true on default java server and running sample-pubsub-2.html from browser.
> The correct implementation should combine the two library requests into one to avoid double-load.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira