Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60696
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain yahoo.com from 77.238.189.199 cause and error)
DomainKey-Status: good
DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=oq4c9gpNNSC6L3QDEItOQBltzvKaImd1qAY4Whl90Ocfj6KugFvbWpAycVsXal+W7lPKSG2s6U4uBmlZzkQabeoSscEPi4oR6sH7jNnFeyZn2aiasRf37wnMegcZJzd/TrHFsfJRuyQj9EZdNOf2QEuFikr5ewi30pNRgpiYTpo=;
References: <1338323273.24780.YahooMailNeo@web29506.mail.ird.yahoo.com> <op.we28irwgidpuyk@damnation.mshome.net> <1338408656.56325.YahooMailNeo@web29506.mail.ird.yahoo.com> <1494709342.20120530171419@cypressintegrated.com>
Message-ID: <1338447482.89411.YahooMailNeo@web29506.mail.ird.yahoo.com>
Date: Thu, 31 May 2012 07:58:02 +0100 (BST)
Reply-To: Christian Ferrari <camauz@yahoo.com>
To: Sanford Whiteman <swhitemanlistens-software@cypressintegrated.com>,
  "internals@lists.php.net" <internals@lists.php.net>
In-Reply-To: <1494709342.20120530171419@cypressintegrated.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] PHP and two phase commit transactions
From: camauz@yahoo.com (Christian Ferrari)

>>  1. Is there any interest in "two phase commit" inside PHP=0A=0A>>  comm=
unity? Without a real interest, every effort would be useless.=0A> =0A> I c=
an't speak to a "critical mass" of interest, but as PHP and =0A> MySQL=0A> =
are closely coupled in the real world, until relatively recently (when=0A> =
Inno became the default) that meant that PHP and MyISAM were best=0A> buds.=
 I don't know how you could do 2PC between two=0A> transaction-unaware back=
 ends. I could see one transaction-aware and=0A> one transaction-unaware wo=
rking by running synchronously w/the=0A> transactional one first (?).=0A=0A=
LIXA can be coupled only with resource managers that supports some form of =
XA protocol. When the resource manager is truly XA compliant (Oracle DBMS, =
IBM DB2, IBM WebSphere MQ) LIXA code is just a wrapper of the XA switch fil=
e provided by the resource manager. When the resource manager is partially =
XA compliant (PostgreSQL, MySQL with InnoDB) LIXA code adds some logic to e=
mulate a standard XA switch file. MySQL itself is affected by this serious =
bug http://bugs.mysql.com/bug.php?id=3D12161 that violates XA specification=
. Despite it, LIXA tries to do its best to support XA for MySQL.=0AMySQl an=
d MyISAM can not be used in conjuction with LIXA for distributed transactio=
n processing.=0A=0A> =0A> So my sense is that PHP, because of MyISAM's ubiq=
uity, isn't the ideal=0A> language target for 2PC (compared to Java/.NET wh=
ere the most=0A> "enterprise" back end is assumed, however inaccurately!). =
=0A> =0A> That doesn't mean there wouldn't be some interest, though.=0A> =
=0A> -- S.=0A> =0A> =0A=0ACh. F.=0A