Thanks Jason! I had seen that thread on the nh persister and wondered if that was what others were tending to do. I really appreciate your response. Mike
On Tue, Sep 22, 2009 at 7:10 PM, Jason Meckley <[email protected]>wrote: > > currently there is only the in-memory saga persister which is good for > testing. the others were removed due to complexity. as a quick fix you > can port the old (SF) saga persister(s) using the lastest bits from > github. i spiked this not too long ago and it worked for my needs. I > did find that executing a saga in a tight loop will cause read/write > errors to Esent. They "work themselves out" with the built in retry > mechanism, but it wasn't ideal if the loop is a common occurrence. > > There was also talk of building a database/Nh enabled saga persister. > really all you need to do is implement ISagaPersister<TSaga> however > you see fit. if not PHT, maybe a database driven persister. > > On Sep 22, 9:47 pm, Mike Nichols <[email protected]> wrote: > > Hi all > > I have been swamped and unable to keep current with RSB changes to > > project structure and design. > > I pulled down the git source and wondered what folks are using for > > ISagaPersister implementations these days since it looks like dht > > isn't being used? > > even a optimistic concurrency strategy would work for me but are you > > all handrolling your own implementation or is there something hiding I > > can't find? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
