| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Vadim Nasardinov <vadimn(at)redhat(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: 1300 to 3100 lines of code for XA support (was: Re: plans |
| Date: | 2004-11-02 20:09:38 |
| Message-ID: | Pine.BSO.4.56.0411021453540.1202@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Tue, 2 Nov 2004, Vadim Nasardinov wrote:
> > With current proposals it doesn't seem like much work on the driver
> > side.
>
> To get a better feel for what "not much work" actually looks like, I
> googled for existing implementations.
>
You might be interested to know that pg used to have a fake XA
implementation in the driver as well.
http://gborg.postgresql.org/project/pgjdbc/cvs/cvs.php/pgjdbc/org/postgresql/xa?sa=1
I don't think a straight lines of code count can really indicate the
difficulty of implementation. If the backend API matches up with the XA
API then you can easily write even thousands of lines of boilerplate code.
If the APIs don't match then you may have to do some complicated mapping.
All of the real work for XA is on the backend side.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2004-11-02 20:18:44 | Re: 1300 to 3100 lines of code for XA support |
| Previous Message | Oliver Jowett | 2004-11-02 20:09:03 | Re: 1300 to 3100 lines of code for XA support |