#well, I think even those in the Perl priesthood acknowledge that it's hard #to scale Perl up. in which case, Python's competitor could be... Java? #
If Python/Zope DOESN'T have support for distributed transactions, I don't think it'll fair in large enterprise applications in the same way Java/J2EE can. The question you have to ask is, what do you do when you need an atomic operation to span multiple databases, and worse across multiple business objects, or services? Database two-phase commits perhaps? But that'll only be for databases, and they all need to be from the same database vendor. e.g. Say you have an online banking solution where in customers can manage accounts from branches all over the world, and each branch has it's own database. Now, what do you do when a customer transfers funds from one account to multiple accounts? Of course considering all failure paths, the application needs to be able to rollback everything (across multiple databases, multiple business object, and services) -- you don't want to substract money from the source account, and not guarantee transfer to other accounts. Would you? ;) The M$ World has Transaction Server (TM), and in the Java/J2EE there's Transaction Services. With both services, all participating entities will all commit, or fail altogether. That may not be the best example, but I hope you get the picture. stay cool. jeff -- -- Jeff Gutierrez http://www.mapua.org http://www.mapua.com http://www.mapua.net Pinoy Ako! May reklamo? _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
