You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Kevin Brown (JIRA)" <ji...@apache.org> on 2008/10/04 00:49:44 UTC
[jira] Created: (SHINDIG-643) Create a single location for root
paths.
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.
[jira] Commented: (SHINDIG-643) Create a single location for root
paths.
Posted by "Kevin Brown (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (SHINDIG-643) Create a single location for root
paths.
Posted by "jeremi Joslin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jeremi Joslin updated SHINDIG-643:
----------------------------------
Attachment: SHINDIG-643.patch
This patch move the configuration of the content-rewrite from the shindig.properties to the container.js in shindig java.
It also enable to have different rewriting for each container.
Can anyone review it?
> 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
> Attachments: SHINDIG-643.patch
>
>
> 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.
[jira] Commented: (SHINDIG-643) Create a single location for root
paths.
Posted by "Karl Matthias (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664605#action_12664605 ]
Karl Matthias commented on SHINDIG-643:
---------------------------------------
The PHP Readme is also out of date on this issue. If I hadn't found this bug with the correct information I could not have set up the server in a path other than webroot.
> 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
> Attachments: SHINDIG-643.patch
>
>
> 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.
[jira] Commented: (SHINDIG-643) Create a single location for root
paths.
Posted by "Vincent Siveton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688122#action_12688122 ]
Vincent Siveton commented on SHINDIG-643:
-----------------------------------------
Jeremi: could you update your patch under the current trunk?
> 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: Java, Javascript , PHP
> Reporter: Kevin Brown
> Attachments: SHINDIG-643.patch
>
>
> 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.
[jira] Commented: (SHINDIG-643) Create a single location for root
paths.
Posted by "Kevin Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648101#action_12648101 ]
Kevin Brown commented on SHINDIG-643:
-------------------------------------
I have a family emergency and will not be available regularly this week.
Contacts:
Production release issues: opensocial-sre, lryan
Sandbox issues: opensocial-eng, awiner
> 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
> Attachments: SHINDIG-643.patch
>
>
> 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.
[jira] Commented: (SHINDIG-643) Create a single location for root
paths.
Posted by "Chris Chabot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638211#action_12638211 ]
Chris Chabot commented on SHINDIG-643:
--------------------------------------
on the php side of things, there are 2 places for this (which imo is 1 to many):
shindig/config/container.js and
shindig/php/config/container.php
i'd be more then happy to base the path construction of the one on the other (doesn't matter so much to me which is the master in this regard, having it in the php config would be easier for the end users, but if that would affect consistency between the 2 versions, imo that's not a sacrifice worth making)
> 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.