On Fri, Feb 19, 2010 at 16:41, Jukka Zitting <[email protected]> wrote: > I'd go even further and drop the callback mechanism. Instead just have > a method like > > TransactionId getLatestTransaction() > > in the persistence layer and have higher level code poll (for > observation listeners, etc.) or explicitly request (for > Repository.login, Session.refresh and Session.save) the latest state > of the repository.
Hmm, but how to make sure to not miss anything in case of concurrent threads? (Maybe I am missing something here, so excuse my question). On Fri, Feb 19, 2010 at 17:05, Jukka Zitting <[email protected]> wrote: > I'd make node type constraints and security checks the responsibility > of the client who commits the transaction. I don't see the point of > doing such steps after the transaction has already been committed. +1 Alex -- Alexander Klimetschek [email protected]
