[jira] [Comment Edited] (TINKERPOP3-869) Adding a UtilityOpProcessor for gremlin-server

["Dylan Millikin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TINKERPOP3-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946460#comment-14946460 ] 

Dylan Millikin edited comment on TINKERPOP3-869 at 10/7/15 7:48 AM:
--------------------------------------------------------------------

Thinking out loud but there might be more merit in making the args:

{code}
{
   "message": "This is an error",
   "code": 500
}
{code}

And skip the extra nesting since the {{op}} is already pretty specific. Thoughts?


was (Author: dmill):
Thinking out loud but there might be more merit in making the args:

{code}
{
   "message": "This is an error",
   "code": 500
}
{code}

And skip the extra nesting. Thoughts?

> Adding a UtilityOpProcessor for gremlin-server
> ----------------------------------------------
>
>                 Key: TINKERPOP3-869
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-869
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: server
>            Reporter: Dylan Millikin
>            Assignee: stephen mallette
>            Priority: Minor
>
> This is a proposal for the addition of a UtilityOpProcessor.
> The initial idea behind this OpProcessor is to allow driver developers to have easier means of testing their error management. But it could extend beyond that.
> The initial implementation would probably possess an op of {{throw}} that would be fed the following {{args}}:
> {code}
> { 
>    "exception": {"message":"This is an error.", "code":500}
> }
> {code}
> Or we could also imagine :
> {code}
> { 
>    "exception": {"class":"OpProcessorException", "message":"This is an error.", "code":500}
> }
> {code}
> Though I'm not sure how useful this would be. And it would probably also have security implications so it's really just here for posterity.
> ---
> After receiving these the server would return the described error as per the driver building documentation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)