Hi!
Question for the group: How much do we care about external dependencies for
the client library? For example, libevent is already being used in the
server, and there is certainly room to use this in the client code. I don't
expect many other external non-core dependencies (if any), but I was curious
if the "use common OSS libs as much as possible" rule applies to the client
lib as well. The reason we may want to keep it dependency free is if it ends
up being built on other systems than the server supports (like windows, but
libevent does work there too).
One other thing I forgot to mention in the first email is that the new client
library will have support for multiple versions of the wire protocol. For
example, we can support any new changes for drizzle alongside the various
MySQL protocols.
I think we care a lot about it. One thing that would be excellent to do
though... Instead of making it require libevent, make it compatible with
other programs which use a libevent main loop. Or at least easier to plug
in ... in order to make libmemcached work you kind of have to set it to
nonblock mode and steal its fd's.
-Dormando
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
