[
https://issues.apache.org/jira/browse/STONEHENGE-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716079#action_12716079
]
Avantika Agrawal commented on STONEHENGE-21:
--------------------------------------------
I was brainstorming some ideas for this configuration system and I think we can
break down the issue of the database configuration system into a bunch of
tickets.
Firstly, I think we should work on implementing Ben's ConfigService contract -
this should get the config service running when we start up StockTrader.
The second step I guess would then be to hook up the .NET StockTrader
configuration to use this ConfigService.
Finally, I think the last step could be to resolve the issue of mutiple
clients. For this we'd need to have the client look itself up in the database
and retrieve its endpoint (along the lines of Ben's new ClientToBS structure.
Let me know what you guys think of this.
> 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
>
> Attachments: ConfigContract.patch
>
>
> 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.
