| From: | Bryan Varner <bvarner(at)polarislabs(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL XAResource & GlassFish 3.1.2.2 |
| Date: | 2013-02-13 21:29:12 |
| Message-ID: | 511C05A8.7060001@polarislabs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
>> I think it's more like the JTA authors expect there to be methods
>> in the underlying FE/BE protocol to associate/disassociate a
>> transaction from the physical connection.
>
> It does seem like we could implement more of the JTA features if an
> XAConnection actually managed its own small pool of database
> connections when necessary. Whether there is enough demand to
> merit the work involved is a whole different question.
Why would each XAConnection need it's own pool?
> If someone wanted it enough to pay for the work, I bet it could be
> done. :-)
This is where I'm supposed to mention that the views expressed in my
emails do not represent the views of POLARIS Laboratories. Right?
Regards,
-Bryan Varner
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2013-02-13 22:05:46 | Re: PostgreSQL XAResource & GlassFish 3.1.2.2 |
| Previous Message | Kevin Grittner | 2013-02-13 20:23:57 | Re: PostgreSQL XAResource & GlassFish 3.1.2.2 |