Skip site navigation (1) Skip section navigation (2)

Maintaining a transaction across multiple HTTP requests

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: "pgsql-php(at)postgresql(dot)org" <pgsql-php(at)postgresql(dot)org>
Subject: Maintaining a transaction across multiple HTTP requests
Date: 2004-06-03 18:46:25
Message-ID: 50E84F4C-95FF-41A7-950B-D44890874BB3@mimectl (view raw or flat)
Thread:
Lists: pgsql-php
Hi all,

I need to write a server script that will be used to synchronise a SQL Server 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 which 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 PostgreSQL since the last synchronisation. If there are any, the script will return details to the client for conflict resolution. When the planned conflict resolution is returned by the client, the required updates are executed within the original transaction which is then committed.

The difficulty with this plan is that the transaction must be maintained across 2 or more individual http requests (which 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?

Regards, Dave.

pgsql-php by date

Next:From: V i s h a l Kashyap @ [Sai Hertz And Control Systems]Date: 2004-06-04 04:05:39
Subject: SSL PostgreSQL and PHP
Previous:From: Christopher Kings-LynneDate: 2004-06-03 01:37:17
Subject: Re: PHP memory usage

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group