[windup-dev] Where to store intermediate data?
Lincoln Baxter, III
lincolnbaxter at gmail.com
Fri Jul 25 15:40:33 EDT 2014
Additionally, if you're looking for a context. Use
GraphRewrite.getRewriteContext() ... it is a map-like structure, but I
don't think we'll need to use it much so consider the various factors
carefully (and discuss if you are unsure) when thinking about putting
information there.
On Fri, Jul 25, 2014 at 3:39 PM, Lincoln Baxter, III <
lincolnbaxter at gmail.com> wrote:
> Ah, also, I didn't say I don't want intermediate data in the graph :) That
> is an over-generalization. I said I don't think *this* data belongs in the
> graph. We do want to be storing the *right* data in the graph. And we need
> to be careful about what that data is and where and how it is stored.
>
>
> On Fri, Jul 25, 2014 at 2:21 PM, Ondrej Zizka <ozizka at redhat.com> wrote:
>
>> Right, but Lincoln doesn't want the intermediate data in the graph, if I
>> understand him correctly.
>> That's why I am looking for some Map in our Java data structures.
>>
>> Ondra
>>
>>
>>
>> On 25.7.2014 20:11, Brad Davis wrote:
>> > Alternative to adding data to the graph vertex directly, you could
>> create a intermediate vertex that has a reference to another vertex you are
>> referring to.
>> >
>> > IntermediateMapVertex -> SomeOtherVertex
>> >
>> > Brad Davis
>> > Red Hat Consulting
>> > Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>> >
>> >
>> > ----- Original Message -----
>> > From: "Brad Davis" <bdavis at redhat.com>
>> > To: "Windup-dev List" <windup-dev at lists.jboss.org>
>> > Sent: Friday, July 25, 2014 2:09:57 PM
>> > Subject: Re: [windup-dev] Where to store intermediate data?
>> >
>> > The Titan implementation already provides caching. When you say a Map
>> like API, you mean to access the data on the nodes?
>> >
>> > >From an intermediate data perspective, you can always get the
>> underlying vertex from the Framed Vertex, and then write to it like a Map
>> (Key, Value pair).
>> >
>> > Brad Davis
>> > Red Hat Consulting
>> > Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>> >
>> >
>> > ----- Original Message -----
>> > From: "Ondrej Zizka" <ozizka at redhat.com>
>> > To: "Windup-dev List" <windup-dev at lists.jboss.org>
>> > Sent: Friday, July 25, 2014 2:02:06 PM
>> > Subject: [windup-dev] Where to store intermediate data?
>> >
>> > Hi,
>> >
>> > where should I cache intermediate data? E.g. the model metadata.
>> > I expected GraphContext to have some Map-like API, there's none.
>> > Should I add it? Or should I clutter the API with it? Or will it be
>> > better to store it in the graph afterall?
>> >
>> > Thanks,
>> > Ondra
>> > _______________________________________________
>> > windup-dev mailing list
>> > windup-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/windup-dev
>> > _______________________________________________
>> > windup-dev mailing list
>> > windup-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/windup-dev
>> > _______________________________________________
>> > windup-dev mailing list
>> > windup-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140725/48d222a8/attachment-0001.html
More information about the windup-dev
mailing list