From: | mephysto <mephystoonhell(at)gmail(dot)com> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Fwd: Postgres JDBC, WS and commit |
Date: | 2012-05-09 19:11:19 |
Message-ID: | 1336590679429-5698263.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Hi Kevin,
I will try to explain my scenario: with my application, many users exchange
message within them. User1 send message to user2 by a web service. This web
service send message and wait the response from user 2 before end and send
notice to user1. I can't know how many time is needed for response, so, I
would to save te state in a table on database to prevent accidental
disconnection of client from web service.
But I found that, if transaction are not closed until web service operation
end, my table are not update, and I can't know the wait state of user1 and I
can't take back he to his request.
Moreover, if transaction lock my table, and other user, user3, send a
message to user4, I can't save his state until user1 operation end.
Is it clear enough?
Is there any wrong in my reasoning? Is there anything I ignore in pool
functionality?
Thanks in advance.
Mephysto
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Postgres-JDBC-WS-and-commit-tp5697657p5698263.html
Sent from the PostgreSQL - jdbc mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2012-05-09 19:21:36 | Re: Fwd: Postgres JDBC, WS and commit |
Previous Message | Kevin Carr | 2012-05-09 17:03:53 | Fwd: Postgres JDBC, WS and commit |