As far I know, this is the way iBATIS works with a single database. It's not slow, because each request has its own separate thread. Furthermore, since iBATIS is running on the server side of your system, there's no difference (from its point of view) if the caller is a swing client or a web front end. You can also benefit of the caching features in a better way.
Regards, Fabrizio -----Messaggio originale----- Da: James, Steven [mailto:[EMAIL PROTECTED] Inviato: venerd́ 20 maggio 2005 13.53 A: ibatis-user-java@incubator.apache.org Oggetto: RE: sqlmapclients 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.
