incubator-stonehenge-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew (Drew) (JIRA)" <j...@apache.org>
Subject [jira] Commented: (STONEHENGE-21) Having a unified configuration system
Date Thu, 07 May 2009 19:26:45 GMT

    [ https://issues.apache.org/jira/browse/STONEHENGE-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707056#action_12707056
] 

Andrew (Drew) commented on STONEHENGE-21:
-----------------------------------------

I like that idea (dotnet config service to use existing tables)
. 
HOWEVER, we need to deal with the issue of having multiple machines and muliple scenarios
I believe the BSTOOPS and the CLIENTTOBS tables only handle one scenario at a time.   We need
to add ClientName and ServerName columns to the tables and I believe that will handle the
issue. The config service would look up the config to be used 'my' machine. 

I am not a db guy so there may be a better way to handle that.

Drew

> Having a unified configuration system
> -------------------------------------
>
>                 Key: STONEHENGE-21
>                 URL: https://issues.apache.org/jira/browse/STONEHENGE-21
>             Project: Stonehenge
>          Issue Type: New Feature
>            Reporter: S.Uthaiyashankar
>             Fix For: M2
>
>
> Currently, .NET Services and PHP/WSAS Services are configured differently. .NET uses
file based configuration and PHP/WSAS uses database configurations. We have to find a common
mechanism to store the configurations. One option is to have a configuration service and then
all the other services request endpoint details from configuration service. 

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


Mime
View raw message