Re: [windup-dev] Where to store intermediate data?

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(a)redhat.com | c: 980.226.7865 | http://www.redhat.com ----- Original Message ----- From: "Brad Davis" <bdavis(a)redhat.com&gt; To: "Windup-dev List" <windup-dev(a)lists.jboss.org&gt; 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(a)redhat.com | c: 980.226.7865 | http://www.redhat.com ----- Original Message ----- From: "Ondrej Zizka" <ozizka(a)redhat.com&gt; To: "Windup-dev List" <windup-dev(a)lists.jboss.org&gt; 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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/windup-dev _______________________________________________ windup-dev mailing list windup-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/windup-dev _______________________________________________ windup-dev mailing list windup-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/windup-dev