[jira] Assigned: (SHINDIG-146) Terminology change: Replace "syndicator" with "container" to be in line with current gadgets terminology.

["Santiago Gala (JIRA)" <ji...@apache.org>]

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

Santiago Gala reassigned SHINDIG-146:
-------------------------------------

    Assignee: Santiago Gala

> 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 (Javascript), Gadget Rendering Server (Java), Gadget Rendering Server (PHP), Sample container & Examples
>            Reporter: Kevin Brown
>            Assignee: Santiago Gala
>         Attachments: SHINDIG-146-for-humans-2.patch, SHINDIG-146-for-humans-3.patch, SHINDIG-146-for-humans-squashed-2.patch, SHINDIG-146-for-humans-squashed-3.patch, SHINDIG-146-for-humans-squashed.patch, SHINDIG-146-for-humans.patch, SHINDIG-146-for-robots-squashed-2.patch, SHINDIG-146-for-robots-squashed-3.patch, SHINDIG-146-for-robots-squashed.patch
>
>
> 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.