Hi Waqas You mentioned in a private email that you'd still want to work on client side query parsing and using the memcache api. That's cool, unless there are some changes there isn't anyone of the GSoC students to work on that.
Just wanted to give you a rough outline of what I would do if I were you. Of course, you might already have done some of these: Find a Java client for Memcache that you like (I think there are more than one, and I don't know which one is the best) Setup a memcached server and write some test program that uses the java memcache client. Now remove memcached server and download MySQL 5.6. Setup the memcache api for MySQL and try to run your test program against this. Learn how to configure different mappings of MySQL tables to the memcache api. After all of the above, take drizzle-jdbc, figure out a place where you could capture the queries and reroute them to the memcache client instead. Start with just a simple example like "SELECT * FROM t WHERE id=?" and then expand from there. I'm sure Marcus will be available to give some pointers. Otoh, don't be afraid to make your own decisions. Just dive into the code, do something, and if you think it works, then submit a patch. Sometimes you might not get a lot of guidance by asking questions by email, but if you submit code (especially if it seems to work) then usually the maintainers will become interested and review your code. This is also how I became involved with Drizzle: If people are busy, don't wait for them, just do something anyway. henrik -- henrik.i...@avoinelama.fi +358-40-8211286 skype: henrik.ingo irc: hingo www.openlife.cc My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559 _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : drizzle-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
