[
https://issues.apache.org/jira/browse/JCLOUDS-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316471#comment-14316471
]
Ignasi Barrera commented on JCLOUDS-819:
----------------------------------------
I don't know if it is good to expose transport specific features in the
ContextBuilder. It should be used to describe the api or view being loaded, but
I wouldn't expose such concrete things there.
I'd rather use a context property or other mechanism to allow users to override
(or bind to the injector) the user agent.
> Allow prepending a custom user agent
> ------------------------------------
>
> Key: JCLOUDS-819
> URL: https://issues.apache.org/jira/browse/JCLOUDS-819
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-core
> Reporter: Everett Toews
> Priority: Minor
>
> Give your users the ability to _prepend_ a custom user agent. So if the
> existing user agent is "jclouds/1.8.1 java/1.7.0_51"
> Provide a method for your users to easily prepend their own user agent so
> they can further customize it. e.g. "users-app/0.1.2 jclouds/1.8.1
> java/1.7.0_51"
> This will give cloud providers much better insight into how people are using
> jclouds. This should be well documented and part of examples that are written
> for jclouds.
> It could be set like,
> {code}
> ComputeServiceContext context = ContextBuilder.newBuilder(PROVIDER)
> .credentials(username, apiKey)
> .userAgent("users-app/0.1.2")
> .buildView(ComputeServiceContext.class);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
