Hi there,
Given this model, each thread is obviously going to want to have
multiple transactions outstanding. Is this something that might be added
to MySQL in future or am I totally overestimating the expense of using
one thread per connection?
I'm guessing you mean that each thread will
Michael McTernan wrote:
Hi there,
Given this model, each thread is obviously going to want to have
multiple transactions outstanding. Is this something that might be added
to MySQL in future or am I totally overestimating the expense of using
one thread per connection?
I'm guessing you
Funny you should mention the totally excellent DBMail - I've deployed it
for quite a few of my clients.
The project I am working on is more of a sod off in the direction of
Exchange. I'm aiming for something collaborative, with a proper backing
store that's easily deployable and an original
checkout http://www.dbmail.org
On Sun, 15 Feb 2004, Chris Nolan wrote:
Hi all,
I'm currently designing an open-source messaging server that will use
MySQL as the data store (in embedded form).
High performance is one of the goals of this project, so I have been
examining possible I/O
Hi all,
I'm currently designing an open-source messaging server that will use
MySQL as the data store (in embedded form).
High performance is one of the goals of this project, so I have been
examining possible I/O models and seem to have settled on a model where
each thread services many
