I would have thought it would be more scaleable to set up a server process (perhaps POE) with a SOAP or HTTP interface to do the threading. Another possibility might be AJAX. > Message: 2 > Date: Tue, 17 Nov 2009 11:22:59 +0000 > From: Mike Tonks <[email protected]> > Subject: [cgiapp] Threading Question > To: CGI Application <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi Folks, > > I'm just considering a problem that I think requires a bit of multi-threading. > > It's a new one for me so wondered if anyone has advice or experience > of using threading with CGI::Application. > > Scenario is: We have 5 database servers at different sites. We would > like to create a search function that queries all of the databases. > The web server is on an intranet and can open connections to all of > the database servers. > > So - I imagine it would be sensible to fire 5 queries on 5 threads, > and wait for them all to return? Then combine the results in some > way. The results sets will be fairly small, say no more than 50 > records. > > Seems likely to be quicker than to fire one, wait for it, fire > another, and so on. > > Also I guess there could be server issues with the use of multiple threads? > > cheers, > > mike > > > >
##### CGI::Application community mailing list ################ ## ## ## To unsubscribe, or change your message delivery options, ## ## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp ## ## ## ## Web archive: http://www.erlbaum.net/pipermail/cgiapp/ ## ## Wiki: http://cgiapp.erlbaum.net/ ## ## ## ################################################################
