[ 
https://issues.apache.org/jira/browse/SHINDIG-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586049#action_12586049
 ] 

Kevin Brown commented on SHINDIG-146:
-------------------------------------

Caja's notion of a container is completely different. Nothing wrong with that, 
it doesn't really matter to us.

The term "syndicator" is synonymous with "container" from the standpoint of the 
opensocial and gadget specs, and the preferred terminology is now "container".

> Terminology change: Replace "syndicator" with "container" to be in line with 
> current gadgets terminology.
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: SHINDIG-146
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-146
>             Project: Shindig
>          Issue Type: Improvement
>          Components: Features, Gadgets Server - Java, Gadgets Server - PHP, 
> Sample container & Examples
>            Reporter: Kevin Brown
>
> Currently, the term "syndicator" (or "synd") is used throughout the code base 
> to refer to container-specific details. This is mostly a terminology holdover 
> from igoogle, and we should move towards renaming these pieces "container" to 
> be in line with current opensocial / gadgets terminology. Suggested changes:
> - Rename SyndicatorConfig classes to ContainerConfig
> - Rename "syndicator" parameters / variables throughout the code base to 
> "container"
> - Rename "synd" URL parameter to "container" -- possibly maintain "synd" as 
> an alias so that existing deployments don't have to be modified.
> The vast majority of shindig deployments will only ever need to support a 
> single container, so most of these changes won't affect those deployments, 
> but for any deployments that support multiple containers (such as 
> gmodules.com), this change will matter.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to