On Tuesday 19 October 2004 16:03, R. Klemme wrote: > > Hi, > > I am developing a web application that accesses MaxDB. > > > > The application has several instances, every instance should be limited > > to a > > number of concurrent sessions to one big MaxDB database instance. So, for > > example: > > > > - Web application Instance "A" should have max. 5 concurrent sessions > > - Web application Instance "B" should have max. 3 concurrent sessions. > > > > How would I do this? I am thinking about giving every web application > > instance > > a seperate username for MaxDB (Security is done in the web application). > > But > > is there a way to limit the number of concurrent sessions per user? > > I'd do it with connection pools. If you're in Java I think you can even > configure he pool in server.xml or in some other XML file. I'd guess you > can then limit the pool size as well as the number of concurrent > connections. It's also not very difficult to roll your owl pool impl that > deals with these contraints but this problem is so general that I am nearly > sure you'll find something out there (or even already built into tomcat).
That's very interesting but our situation here is not that simple: We are migrating from a native C-Client that accesses via ODBC to Zope (Python). The Problem is that during the transistion phase both should be able to access the database, the C-Client and Zope (via Python) but both should have the same pool of concurrent connections. So it would be best if the database itself would handle all this. Best Regards, Hermann -- [EMAIL PROTECTED] GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7 -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
