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 Fri, 08 May 2009 05:42:45 GMT

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

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

I think all we need for the CLEINTTOBS table is to have add a key column "client" and use
the exisitng column (in that row) for the actual endpoint.. So each row int the table will
specify both ends of the connection.  A client will look in the table for "its own" name (key)
and use the endpoint in that row . 

Similar proceedure for BSTOOPS

Then we can have N clients and N services working at the same time with very little effort.



> 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