[
https://issues.apache.org/jira/browse/STONEHENGE-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707347#action_12707347
]
Ben Dewey commented on STONEHENGE-21:
-------------------------------------
Just to be clear. what should the client key be?
1. the client endpoint address - http://st-dev01/trade, or
http://st-dev01:8080/trade
2. just the computer name - st-dev01
3. a unique key (unique name, guid, id)
I'm thinking number #1,
But on that note, why would we add a column to CleintToBs? wouldn't the
endpoint negate the PHP_CLIENT value that's presently there.
So, instead of
client-id | client | bs
http://st-dev01:8080/traderclient | PHP_CLIENT | PHP_BS
http://st-dev01/trade | DOTNET_CLIENT | DOTNET_BS
We could just have, the above is alittle redundant
http://st-dev01:8080/traderclient | PHP_BS
http://st-dev01/trade | DOTNET_BS
-------------------------------------------------
Unfortunately, that takes away your normalization, So my recommendation is:
Add the CLIENT entries to the SERVICES table, So in the SERVICES table you
have DOTNET_CLIENT = http://dev/trade, or DOTNET_CLIENT_1 = http://dev01/trade,
DOTNET_CLIENT_2 = http://dev02/trade
Then your ClientToBs tables can just have rows added for multiple clients.
so your ClientToBs table would look like this
CLIENT | BS
---------------------
DOTNET_CLIENT_1 | PHP_BS
DOTNET_CLIENT_2 | DOTNET_BS
etc.
This would take coding changes on both the dotnet side and php side, as you
would have to lookup your own endpoint, before finding your BS.
> 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.
