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 (Updated) (JIRA)" <ji...@apache.org> on 2011/10/12 10:11:12 UTC

[jira] [Updated] (SHINDIG-1585) Avoiding MetaData Lookup in gadget creation

     [ https://issues.apache.org/jira/browse/SHINDIG-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hasan Ceylan updated SHINDIG-1585:
----------------------------------

    Attachment: pubsub.patch

A Patch to resolve this issue.

1) Adds requiresPubsub2 to Gadget object. 
2) Checks the existence of this parameter in the Gadget
3) If exists takes the requirement from Gadget 
4) If does not exists then makes a metadata lookup

Regards,
Hasan Ceylan
                
> Avoiding MetaData Lookup in gadget creation 
> --------------------------------------------
>
>                 Key: SHINDIG-1585
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1585
>             Project: Shindig
>          Issue Type: Improvement
>          Components: Javascript 
>    Affects Versions: 2.0.2
>            Reporter: Hasan Ceylan
>            Priority: Trivial
>         Attachments: pubsub.patch
>
>
> I have recently became deeply involved with Shindig.
> While observing code, I noticed that in order to decide to use OAAIfrGadget or IfrGadget implementation, container makes a metadata request for each and every gadget on the page.
> Considering the nature of the way opensocial is designed, which already produces a lot of HTTP requests, IMHO every request avoidance counts. I think this one can be avoided easily. A similar handling, the initial height of the iframe is also a load time parameter that affects the way the final html markup generated (inserting height attribute to iframe tag). 
> Therefore, introducing a parameter in the gadget params - say 'pubsubEnabled' -, I can pass that parameter during the creating of the javascript chunk within the page and avoid the metadata lookup iff this parameter exists. In the absence of the parameter, the current implementation might commence.
> If you appreciate the added value here, I would like to get down to coding of this implementation.
> Regards,
> Hasan Ceylan

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira