Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
EventGraph
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post will appear after it is approved by moderators
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Stephen Mallette  
View profile  
 More options May 15 2012, 7:42 pm
From: Stephen Mallette <spmalle...@gmail.com>
Date: Tue, 15 May 2012 16:42:23 -0700 (PDT)
Local: Tues, May 15 2012 7:42 pm
Subject: [Blueprints] EventGraph

All this heavy refactoring of Blueprints has created a lot of turmoil but
has also created opportunities to correct a number of long-standing issues.
 One such problem recently solved was with EventGraph.  

Prior to this refactoring effort, the EventGraph wrapper did not consider
transactions when firing events.  Events fired as changes to the graph
occurred.  If an error occurred and a transaction failed the events would
still have fired even though the transaction rolled back.  With the recent
changes to transactions that introduced the new BufferGraph wrapper, it
then became possible to introduce the new EventGraph implementations:
EventTransactionalGraph and EventTransactionalIndexableGraph.  These new
wrappers raise the same events that the original EventGraph wrapper did,
but queue the events while a transaction is in progress and wait for a
successful commit before the events are fired.

On to Rexster work next!

Best regards,

Stephen


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »