[
https://issues.apache.org/jira/browse/STONEHENGE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas A Hauenstein updated STONEHENGE-78:
--------------------------------------------
Attachment: STONEHENGE-78.zip
Attached is a patch for the .NET client that implements one approach. It is a
purely client-side approach that does not modify service contracts at all.
It does have two dependencies:
- Calls to the configuration service to determine current configuration
- Optional images for each platform included in the Images directory on the
client
It keeps the calls to the configuration service down by caching the current
configuration, and the path to representative images (if any). The cache is
invalidated 5 minutes after last access, or in the event that the configuration
changes.
In the case that images for a platform are not provided, a text label is
displayed with the name of the current endpoint being used (e.g., METRO_BS).
> 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
>
> Attachments: STONEHENGE-78.zip
>
>
> 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.
