[
https://issues.apache.org/jira/browse/STONEHENGE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731174#action_12731174
]
Harold Carr commented on STONEHENGE-78:
---------------------------------------
Rather than depend of the config service, do:
These icons would be retrieved from the web services themselves:
UI -> bs.getBSIcon()
UI -> bs.getOPSIcon() -> ops.getOPSIcon
Each implementation (e.g., .NET, WSO2/Java/PhP, Metro) would then supply a
unique icon.
That way no new dependency is introduced, just some new methods on existing
services.
> Add a footer to the .NET and PHP Clients that display the current config
> ------------------------------------------------------------------------
>
> Key: STONEHENGE-78
> URL: https://issues.apache.org/jira/browse/STONEHENGE-78
> Project: Stonehenge
> Issue Type: Improvement
> Components: DOTNET_CLIENT, PHP_CLIENT
> Reporter: Ben Dewey
> Assignee: Ben Dewey
> Fix For: M2
>
>
> I was giving the interop demo in front of a live audience tonight and we felt
> that it would be a nice feature to include the current configuration in the
> footer of the .net and php client.
> Pros:
> - You can refresh and quickly see at a glance how the configuration is setup
> Cons:
> - Doesn't fit into the design, (although were demonstrating function not
> design)
> - Requires an extra calls to the config service
> - Creates a dependency from trade client to GetBSConfig
> I think the pro out weighs the con. Any thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
