Each call that goes into the server is it's own thread. So, there should be no issue. It's the same as though you were accessing via a servlet based front end. With the web you have a bunch of users calling only one sqlmap client. I don't see where this would be a problem. Are you running into some issues that would indicate otherwise?
Brandon On 5/20/05, James, Steven <[EMAIL PROTECTED]> wrote: > Thanks for the reply i think i need to futher explain i think. My gui connect > to a rpc server which has an ibatis layer > and one sqlclient. All the clients that can concurrently connect to the db > share the same sqlmapclient. > > SWT GUI Clients --> rcp persisted middle ware -> ibatis > > Does mean i need a sqlmap per client will this not be slow. And is there a > limit.. > > Steve.. > > -----Original Message----- > From: Fabrizio Gianneschi [mailto:[EMAIL PROTECTED] > Sent: Fri 5/20/2005 12:00 PM > To: ibatis-user-java@incubator.apache.org > Subject: R: sqlmapclients > > Since each SqlMapClient instance is related to a single database, but can > support many client requests (see cfg file), I think you'd not have to > provide an instance for each client, until they use the same db. > > Fabrizio > > -----Messaggio originale----- > Da: James, Steven [mailto:[EMAIL PROTECTED] > Inviato: venerd́ 20 maggio 2005 12.52 > A: ibatis-user-java@incubator.apache.org > Oggetto: sqlmapclients > > For each gui client connecting to a server is it better to have a > sqlmapclient for each or a shared client for all. > > steve.. > This e-mail and any attachment is for authorised use by the intended > recipient(s) only. It may contain proprietary material, confidential > information and/or be subject to legal privilege. It should not be copied, > disclosed to, retained or used by, any other party. If you are not an > intended recipient then please promptly delete this e-mail and any > attachment and all copies and inform the sender. Thank you. > > > > This e-mail and any attachment is for authorised use by the intended > recipient(s) only. It may contain proprietary material, confidential > information and/or be subject to legal privilege. It should not be copied, > disclosed to, retained or used by, any other party. If you are not an > intended recipient then please promptly delete this e-mail and any attachment > and all copies and inform the sender. Thank you. >
