[
https://issues.apache.org/jira/browse/TINKERPOP3-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP3-712.
---------------------------------------
Resolution: Won't Fix
Wasn't as easy as I thought. The current approach to doing this is bound to
the authentication process. Will leave this as-is for now and wait for a more
specific use case to pop up before considering a change.
> Place the RequestMessage in Gremlin Server Channel Attributes
> -------------------------------------------------------------
>
> Key: TINKERPOP3-712
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-712
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.0.0-incubating
> Reporter: stephen mallette
> Assignee: stephen mallette
> Priority: Minor
>
> When the server receives a {{RequestMessage}} it is passed along the pipeline
> until it gets processed and {{ResponseMessage}} objects are written back
> down. After construction of the {{ResponseMessage}} the context of the
> {{RequestMessage}} is "lost" to downstream handlers (short of the request
> id). For those writing custom handlers it might be useful to have that
> {{RequestMessage}} available in the channel attributes in case it was needed
> for something.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
