From ccacb2de3ce7a4422cd550a392841ad2ef0fdc09 Mon Sep 17 00:00:00 2001 From: Brian Lopez Date: Wed, 7 Apr 2010 10:47:16 -0700 Subject: [PATCH] a couple more notes about async --- README.rdoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.rdoc b/README.rdoc index 395c363..9e1a5ff 100644 --- a/README.rdoc +++ b/README.rdoc @@ -71,8 +71,9 @@ like EventMachine or even IO.select. Once the socket becomes readable, you can d # result will be a Mysql2::Result instance result = client.async_result -NOTE: Because of the way MySQL's query API works, this method will block until the result is ready no matter what. +NOTE: Because of the way MySQL's query API works, this method will block until the result is ready. So if you really need things to stay async, it's best to just monitor the socket with something like EventMachine. +If you need multiple query concurrency take a look at using a connection pool. == Compatibility