[
https://issues.apache.org/jira/browse/SHINDIG-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638329#action_12638329
]
Kevin Brown commented on SHINDIG-643:
-------------------------------------
My vote is for putting into container config, for 4 reasons:
1. Consistency between client and server configuration
2. Consistency between Java & PHP implementations
3. Consistency in our support for deployments that need to support multiple
containers.
4. Consistency in locating configuration options.
Ideally, I'd like the only PHP or java-specific configuration to be pointers to
the locations of the features.xml & container configuration files, and details
that are actually language specific and simply don't exist in other
implementations. Anytime where we have to document two different ways to
configure the same thing, it hurts our users.
> Create a single location for root paths.
> ----------------------------------------
>
> Key: SHINDIG-643
> URL: https://issues.apache.org/jira/browse/SHINDIG-643
> Project: Shindig
> Issue Type: Improvement
> Components: Common Components (Java), Common Components (PHP),
> Features (Javascript), Gadget Rendering Server (Java), Gadget Rendering
> Server (PHP), OpenSocial feature (Javascript), RESTful API (Java), RESTful
> API (PHP), Sample container & Examples
> Reporter: Kevin Brown
>
> Currently there are at least 12 places where you can potentially have to
> configure urls for running Shindig. We need to standardize how these are
> going to be handled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
