Date: Wed, 28 Apr 2010 12:55:38 +0100 From: Karl Pielorz <kpielorz_lst@tdx.co.uk> To: Alfred Perlstein <alfred@freebsd.org> Cc: freebsd-threads@FreeBSD.org Subject: Re: Advice / best practice - thread connection pools / mutexes Message-ID: <BA117CBD0D3A7158C40514FE@HPQuadro64.dmpriest.net.uk> In-Reply-To: <20100428111226.GK35381@elvis.mu.org> References: <6AD0A971B01FA1DE632BAF65@HPQuadro64.dmpriest.net.uk> <20100428111226.GK35381@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--On 28 April 2010 04:12 -0700 Alfred Perlstein <alfred@freebsd.org> wrote: > The most simple method is to do the following at startup: > > [snip wonderful sample code] > > This should provide for a connection pool, each thread > can then call get_con() to get a connection, and should > call put_con() when done with it. > > good luck. > -Alfred Thanks, that looks pretty much exactly what I'm looking for - thanks also to the other people who replied, I've certainly got a few options now (which is a big improvement on what I had before!). Regards, -Karl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BA117CBD0D3A7158C40514FE>