On 11/6/07, Klas Ehnrot <[EMAIL PROTECTED]> wrote: > Hi! > > I'm about to finish up the last two topics for the design guide and > need your input.
Great! > > Regarding transactions usage, what do you think should be highlighted? > > 1. Once again showing how transaction handling is setup in Neo? > Already done in the other guides and in the API == redundant? I do NOT think it's redundant. We've been very poor at *explaining* our transaction idiom. rather than just *displaying* it to people, as evidenced for example by the discusisons in ticket #12. (https://trac.neo4j.org/ticket/12) > > 2. Showing nestled transactions, emphasizing to not assume that the > caller of a method has setup a transaction? Yup, and if you use our Transaction class in the idiomatic way, it'll Just Work(tm) even if the enclosing method has already opened a tx. This is good. But we should also emphasize, as Tobias pointed out, that we don't support *real* nested transactions. I think this is ok (the price/performance ratio of implementing nested tx doesn't suggest to me that it's a high prio issue). But we should be very clear about the maybe not-so-obvious semantics of Transcation in our documentation. > > 3. Connecting Neo transactions with transaction managers for JEE > appservers (Websphere, JBoss, etc.) Has this been done? Any example > code/configuration to share? Is this a suitable topic for the design > guide? > > 3. More advanced topics? Maybe not suitable for a first design guide? I don't either one of the 3s are suitable for the design guide. :) As for the container, we haven't done a lot of TM compatibility testing yet. We're running Spring in a project so hopefully we'll get some feedback there. Cheers, -- Emil Eifrém, CEO [EMAIL PROTECTED] Neo Persistence AB, www.neopersistence.com Cell: +46 733 462 271 | US Cell: 206 403 8808 _______________________________________________ Neo mailing list User@lists.neo4j.org http://lists.neo4j.org/mailman/listinfo/user
