[
https://issues.apache.org/jira/browse/TINKERPOP-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300416#comment-15300416
]
Marko A. Rodriguez commented on TINKERPOP-1311:
-----------------------------------------------
Right now, {{Traverser.detach()}} is simply:
{code}
@Override
public Admin<T> detach() {
this.t = ReferenceFactory.detach(this.t);
return this;
}
{code}
More flexibility on which factory to use would open up "a whole new world... a
new fantastic point of view."
> AttachableFactory and its entailments.
> --------------------------------------
>
> Key: TINKERPOP-1311
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1311
> Project: TinkerPop
> Issue Type: Improvement
> Components: structure
> Affects Versions: 3.2.0-incubating
> Reporter: Marko A. Rodriguez
>
> I think that {{ReferenceXXX}}, {{DetachedXXX}}, and {{StarXXX}} should all
> implement both {{Attachable}} and have a respective {{AttachableFactory}}.
> With proper interfaces, providers can create their own {{ProviderXXX}}
> attachables to be used in OLAP and OLTP as they please. For instance, I'm
> already seeing that I can solve the {{path.by("name")}} problem in OLAP by
> using {{DetachedXXX}} where appropriate in a traversal. Or, if its
> {{path.by(outE().count())}}, then {{StarXXX}}. In other words,
> detaching/attaching should be really flexible, dynamic, and we can come up
> with all sorts of sweet attachables that are optimized for every nook and
> cranny case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
