Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60692
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain cypressintegrated.com designates 69.28.242.152 as permitted sender)
Date: Wed, 30 May 2012 17:14:19 -0400
Reply-To: Sanford Whiteman <swhitemanlistens-software@cypressintegrated.com>
Message-ID: <1494709342.20120530171419@cypressintegrated.com>
To: internals@lists.php.net <internals@lists.php.net>
In-Reply-To: <1338408656.56325.YahooMailNeo@web29506.mail.ird.yahoo.com>
References: <1338323273.24780.YahooMailNeo@web29506.mail.ird.yahoo.com> <op.we28irwgidpuyk@damnation.mshome.net> <1338408656.56325.YahooMailNeo@web29506.mail.ird.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHP and two phase commit transactions
From: swhitemanlistens-software@cypressintegrated.com (Sanford Whiteman)

> 1. Is there any interest in "two phase commit" inside PHP
> community? Without a real interest, every effort would be useless.

I can't speak to a "critical mass" of interest, but as PHP and MySQL
are closely coupled in the real world, until relatively recently (when
Inno became the default) that meant that PHP and MyISAM were best
buds. I don't know how you could do 2PC between two
transaction-unaware back ends. I could see one transaction-aware and
one transaction-unaware working by running synchronously w/the
transactional one first (?).

So my sense is that PHP, because of MyISAM's ubiquity, isn't the ideal
language target for 2PC (compared to Java/.NET where the most
"enterprise" back end is assumed, however inaccurately!). 

That doesn't mean there wouldn't be some interest, though.

-- S.