[jira] [Updated] (TINKERPOP3-712) Place the RequestMessage in Gremlin Server Channel Attributes

["stephen mallette (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TINKERPOP3-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette updated TINKERPOP3-712:
----------------------------------------
         Assignee: stephen mallette
    Fix Version/s: 3.1.0-incubating
          Summary: Place the RequestMessage in Gremlin Server Channel Attributes  (was: Consider Placing the RequestMessage in Channel Attributes)

This was technically already done as part of the addition of SASL authentication.  Just need to adjust a few things and test a bit.

> 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
>             Fix For: 3.1.0-incubating
>
>
> 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)