You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Marko A. Rodriguez (JIRA)" <ji...@apache.org> on 2016/10/12 21:31:20 UTC

[jira] [Created] (TINKERPOP-1501) Consider BytecodeStrategies

Marko A. Rodriguez created TINKERPOP-1501:
---------------------------------------------

             Summary: Consider BytecodeStrategies
                 Key: TINKERPOP-1501
                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1501
             Project: TinkerPop
          Issue Type: Improvement
          Components: language-variant, process
    Affects Versions: 3.2.2
            Reporter: Marko A. Rodriguez


Currently {{TraversalStrategies}} act on {{Traversal}} objects. However, it might be worth pushing some of the optimization "client side" by having {{BytecodeStrategies}} which operate on the bytecode prior to sending it over the wire. Examples could include:

{code}
IdentityRemovalStrategy
AdjacentToIncidentStrategy
IncidentToAdjacentStrategy
RangeByIsCountStrategy
FilterRankStrategy
InlineFilterStrategy
{code}

...in this way, these bytecode-based implementations would mutate the bytecode and then on the server-side, there is less work for the registered {{TraversalStrategies}} to do and thus, less load on the server.



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