--_9BF71BCA-A4D6-4170-A3EF-7600D1DECEC4_
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi all,
I need to write a server script that will be used to synchronise a SQL Serv=
er CE database on a Pocket PC with a central PostgreSQL database. Ideally, =
what I'd like to do is pass modifications made on the PPC to the script whi=
ch then begins a transaction (thus ensuring no futher data changes will be =
seen by the client) and checks for any conflicts with changes made on Postg=
reSQL since the last synchronisation. If there are any, the script will ret=
urn details to the client for conflict resolution. When the planned conflic=
t resolution is returned by the client, the required updates are executed w=
ithin the original transaction which is then committed.
The difficulty with this plan is that the transaction must be maintained ac=
ross 2 or more individual http requests (which may normally be serviced by =
different Apache child processes of course, thus preventing storage of a co=
nnection handle in a session variable). Is there conceivable way I can achi=
eve this, or should I go back to the drawing board?
Regards, Dave.
--_9BF71BCA-A4D6-4170-A3EF-7600D1DECEC4_
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<HTML dir=3Dltr><HEAD></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#000000 size=3D2>Hi all,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I need to write a server script that will =
be used to synchronise a SQL Server CE database on a Pocket PC with a centr=
al PostgreSQL database. Ideally, what I'd like to do is pass modifications =
made on the PPC to the script which then begins a transaction (thus ensurin=
g no futher data changes will be seen by the client) and checks for any con=
flicts with changes made on PostgreSQL since the last synchronisation. If t=
here are any, the script will return details to the client for conflict res=
olution. When the planned conflict resolution is returned by the client, th=
e required updates are executed within the original transaction which is th=
en committed.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The difficulty with this plan is that the =
transaction must be maintained across 2 or more individual http requests (w=
hich may normally be serviced by different Apache child processes of course=
, thus preventing storage of a connection handle in a session variable). Is=
there conceivable way I can achieve this, or should I go back to the =
drawing board?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Regards, Dave.</FONT></DIV></BODY></HTML>
--_9BF71BCA-A4D6-4170-A3EF-7600D1DECEC4_--
