Brian Aker wrote:
Hi!
On Aug 10, 2008, at 8:27 AM, Jeremy Zawodny wrote:
Anyway, we talked a bit about the replication protocol and possibly
moving to something more flexible like protocol buffers[1] or
Thirft[2]. That'd be handy, since I've occasionally had a desire in
the past to whip up a Perl client that can speak MySQL replication.
I want the data coming out of replication to be completely open. The
server should be using the same library that any other client can make
use of.
Right now I am experimenting with buffers, and they seem to do the
trick. If I can get a working prototype this week of how we can use
them in the server then I will have hit my target.
would it make sense to use protocol buffers/thrift as the regular client
API instead of the current protocol?
Cheers,
-Brian
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
