[
https://issues.apache.org/jira/browse/SHINDIG-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086695#comment-13086695
]
Hasan Ceylan commented on SHINDIG-1581:
---------------------------------------
Hello Henry,
First of all I appreciate the prompt handling of the bug I have submitted.
I see that I lot of stuff has changed 3.0 development.
As for your request, unless I am making a terrible mistake, almost none of the
samples (which include rpc as this reflects the bug best) work when I switch to
trunk.
Based on your advise, I will be happy to provide a patch for the trunk?
Best Regards,
Hasan Ceylan
> 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
