t;> >>
>> >> I'm not familiar enough with the TinkerPop code yet to claim that, so
>> >> probably I could be wrong.
>> >> I will need to research it a bit more to find out but I think that
>> Pieter
>> >> is most likely right about a massive
ssor/rxjava/src/main/java/org/apache/tinkerpop/machine/processor/rxjava
> >>
> >> but the process didn't go as far as I understand. I guess it would be
> >> good to know if we want to completely rewrite TinkerPop in version 4 or
> not.
> >>
> >> If we want t
ted by a graph
> > > > > > provider
> > > > > > >>
> > > > > > >> Future executeAsync(Callable func);
> > > > > > >>
> > > > > > >> public default Future asyncNext(){
> > > > > > >>
> >> good to know if we want to completely rewrite TinkerPop in version 4 or
> not.
> >>
> >> If we want to completely rewrite TinkerPop in version 4 then I assume it
> >> may take quite some time to do so. In this case I would be more likely
> to
> >>
gt; > > >>
> > > > >> I'm not familiar enough with the TinkerPop code yet to claim
> > > > that, so
> > > > >> probably I could be wrong.
> > > > >> I will need to research it a bit more to find
start the ball rolling.
>>> >> I think we either need to try to implement async execution in
>>> TinkerPop 3
>>> >> or start making some concrete decisions regarding TinkerPop 4.
>>> >>
>>> >> I see Marko A. Rodriguez started to w
write TinkerPop in version 4
>> or not.
>> >>
>> >> If we want to completely rewrite TinkerPop in version 4 then I assume
>> it
>> >> may take quite some time to do so. In this case I would be more likely
>> to
>> >> say
t; If we want to completely rewrite TinkerPop in version 4 then I
> > assume it
> > >> may take quite some time to do so. In this case I would be more
> > likely to
> > >> say that it's better to implement async functionality in
> > TinkerPop 3 even
> > &
o rewrite the whole functionality then I guess we could try to
> >> work on TinkerPop 4 by introducing async functionality and maybe
> applying
> >> more breaking changes in places where it's better to re-work some parts.
> >>
> >> Best regards,
> >> Ole
;>
>> Best regards,
>> Oleksandr
>>
>>
>> On Thu, Jul 28, 2022 at 7:47 PM pieter gmail
>> wrote:
>>
>>> Hi,
>>>
>>> Does this not imply a massive rewrite of TinkerPop? In particular the
>>> iterator chaining
ork some parts.
>
> Best regards,
> Oleksandr
>
>
> On Thu, Jul 28, 2022 at 7:47 PM pieter gmail
> wrote:
>
>> Hi,
>>
>> Does this not imply a massive rewrite of TinkerPop? In particular the
>> iterator chaining pattern of steps should follow a re
gt; iterator chaining pattern of steps should follow a reactive style of
> coding?
>
> Cheers
> Pieter
>
>
> On Thu, 2022-07-28 at 15:18 +0100, Oleksandr Porunov wrote:
> > I'm interested in adding async capabilities to TinkerPop.
> >
> > There were many
Hi,
Does this not imply a massive rewrite of TinkerPop? In particular the
iterator chaining pattern of steps should follow a reactive style of
coding?
Cheers
Pieter
On Thu, 2022-07-28 at 15:18 +0100, Oleksandr Porunov wrote:
> I'm interested in adding async capabilities to Tinker
hu, Jul 28, 2022 at 7:18 AM Oleksandr Porunov <
alexandr.poru...@gmail.com> wrote:
> I'm interested in adding async capabilities to TinkerPop.
>
> There were many discussions about async capabilities for TinkerPop but
> there was no clear consensus on how and when it should b
I'm interested in adding async capabilities to TinkerPop.
There were many discussions about async capabilities for TinkerPop but
there was no clear consensus on how and when it should be developed.
The benefit for async capabilities is that the user calling a query
shouldn't need its thread
15 matches
Mail list logo
