Ok,
Thanks for the answers....no more questions :)
Ian
On 31 Mar 2008, at 19:10, Kevin Brown wrote:
------=_Part_30423_28565726.1206987008759
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On Mon, Mar 31, 2008 at 10:05 AM, Ian Boston <[EMAIL PROTECTED]> wrote:
When you say threadsafe client does that mean a client in the same
JVM or a remote client (I am being dumb :) ) ?
I mean your Oracle / MySQL / whatever client needs to be. If you're
using a
standard wrapper you're probably already covered anyway.
Does Shindig implement its own transaction monitor (like Jackrabbit
does), so that 1 shared connection is used concurrently by multiple
request transactions ?
That would be left up to the data tier (your implementation).
Shindig just
calls the interfaces as the requests come in. If you want to recycle
connections you're free to do so.
or by shared connection do you mean a connection that is used by 1
request transaction, and returned to a pool to be re-used by the
next.... but during the request transaction is used to perform
multiple overlapping SQL queries ?
By "shared connection" I mean the general term -- that is, there's
only one
connection between each machine, so even if Shindig is serving several
hundred simultaneous requests, all those requests go through the same
database connection.
Guice is cooool, I wa
