Look at the MiddleKit User's Guide from CVS -- it documents some additional
settings that were added in CVS since Webware 0.7 was released. Here's a
In particular, check out the SQLConnectionPoolSize setting which will enable
MiddleKit to use a pool of connections.
> -----Original Message-----
> From: Stefan Miller [mailto:MillerSt@...]
> Sent: Tuesday, July 09, 2002 6:26 PM
> To: webware-discuss@...
> Subject: [Webware-discuss] Middlekit Connection Handling
> Hello all,
> first of all I would like to thank for the great contribution
> to the community. I'm quite new to python and webware as
> well. To exercise myself I'm implementing Interbase database
> access to MiddleKit right now.
> The default model setting is 'threaded'. What does this mean
> exactly? The kinterbasdb database layer for Interbase access
> for python defines threadsafety = 1. So, running a simple
> MiddleKit example as main module, every database access
> results in a new connection as connectionAndCursor is never
> called with connection information passed. Even saveChanges
> creates connections for every single insert, update and
> delete action. Could you please throw a light on that behaviour?
> Thanks in advance,
> Sorry; I posted this before but never saw it on the discussion list.
> All inclusive! 100 MB Speicher, SMS 50% gunstiger, 32 MB
> Preisvorteile und mehr unter http://club.web.de/?mc=021104
> This sf.net email is sponsored by:ThinkGeek
> Stuff, things, and much much more.
> Webware-discuss mailing list