tinkerpop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Divij Vaidya (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TINKERPOP-2243) Add user-agent to RequestOptions
Date Tue, 18 Jun 2019 04:05:00 GMT

    [ https://issues.apache.org/jira/browse/TINKERPOP-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16866209#comment-16866209

Divij Vaidya commented on TINKERPOP-2243:

I would take it a step further and say that driver should have an option where the provider
can add specific custom fields to the request header. It might be a user-agent or an auth
token or encoding of the request data. It could be done by allowing the providers to provide
a JAR which would contain a netty handler adhering to a specific interface and would be auto-magically
picked up by the client on startup.

> Add user-agent to RequestOptions
> --------------------------------
>                 Key: TINKERPOP-2243
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2243
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: driver, server
>    Affects Versions: 3.4.2
>            Reporter: Bryn Cooke
>            Priority: Major
> It would beĀ useful to know the 'user-agent' that is sending a request so that the server
can react in different ways. For instance:
>  * To log differently.
>  * To give different error messages.
> For instance, if the user is connecting via gremlin console then error messages can include
gremlin console specific help.

This message was sent by Atlassian JIRA

View raw message