durusmail: quixote-users: Controlled display of forms & widgets.
Controlled display of forms & widgets.
2003-04-25
2003-04-25
2003-04-28
Controlled display of forms & widgets.
Gerhard Haering
2003-04-25
Etienne Posthumus wrote:
>
> On Friday, Apr 25, 2003, at 03:25 Europe/Amsterdam, Gerhard Häring wrote:
>
>> I'm deloping such a beast myself currently (with pyPgSQL, of course
>> ;-). How do you handle database connections? Do you use a connection
>> pool of some sorts? Is there a usable premade one or did you build it
>> yourself?
>>
>> Can I have concurrent requests with Quixote, anyway? In production, I
>> currently use the Medusa thingie, but in production I'd like to use
>> the SCGI adapter. Do each of these do multithreading? A look into the
>> source code didn't get me an immediate answer.
>
>
> Just a note from the peanut gallery;
> I am using sqlite + medusa + Quixote and trying to stay away from
> multi-threading.
> The dicussions from the 'threads are evil' camp have convinced me enough
> to try and stay away from them as much as possible, by design. [...]

Sure, threads can be quite a hassle. But an application server that
canot handle more than one concurrent request doesn't sound like a good
idea to me, either. For anything but low-profile and toy web projects,
that's not acceptable. From the standpoint of the web framework user
threading will happen transparently, anyway.

My question was if SCGI for example uses threading internally or if I'm
stuck with one (1) concurrent request when using SCGI as a Quixote
backend? How about mod_python?

Anybody can answer this, pleaaaase?

May I ask how you're using SQLite? Using PySQLite or with a custom
wrapper? Do you have any experience with asynchronous access and sqlite?
As a PySQLite developer, I'd be interested in feedback in this area.

-- Gerhard

reply