El Jueves, 17 de Diciembre de 2009, Iñaki Baz Castillo escribió: > Hi, AFAIK Ruby C mysql dirver is blocking so Ruby must wait until get a > response. > So what's the advantage of using "single_threaded = false"? With this > option Sequel creates a pool of connections to the DB while when using > "single_threaded = true" it just mantain a single connection. Is it right? > > Would it be advantages if I use mysqlplus with is async? then should I use > single_threaded or not? > > Also there is a mysql driver on top of EventMachine: > http://github.com/tmm1/em-mysql > > In the README it's supposed to work with Sequel, but I don't understand if > it's works in a transparent way or if I must refactor my code to make it > events based. Any comment about it please? > > The fact is that I'm building a HTTP server based on Thin which uses > EventMachine (event based) for request handling. So I must also use event > based style for responses handling (without blocking calls). What is the > best approach to achieve it using Sequel? should I use mysqlplus and/or > em-mysql? > > Thanks a lot for any help.
I've found a very interesting thread about Sequel and em-mysql: http://www.mail-archive.com/[email protected]/msg01422.html -- Iñaki Baz Castillo <[email protected]> -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
