-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brian Aker wrote: > Hi! > > On Apr 2, 2009, at 11:16 PM, Eric Day wrote: > >> strange that table classes are in the same directory as replication >> classes. > > The table proto is/should be used to transfer the "create table" over > the wire in replication. > > Is it better to have one library that gives you access to all of our > message formats, or is it better to separate these out?
I believe a single library (libdrizzlemessage) is the appropriate way to handle this. Luckily, GPB handles versioning very well, so interfaces *do not* change for the objects even when members are modified or added. So, this means if we build a library with a bunch of classes, and someone links with that library, even if another library is released and installed, old code will still work with the new library without any recompile. That said, libdrizzlemessage should be *the* library which developers include when they want to extend or work with the kernel outside of the facilities provided by libdrizzle. Basically, libdrizzle provide communication facilities for a client to communicate with the server over the wire, and libdrizzlemessage provide facilities for external modules to send and receive common messages the server uses without having to use any protocol. Over time, the combination of the two libraries will add incredible flexibility and power to the module developer. > This may be a "time will tell" sort of situation. Creating a hierarchy > of message formats is required for protobuf since we can then use them > as collections in the code. Yes, and the documentation of those classes is critical. Luckily, the generated code from protoc has doxygenated comments, so the code is already well documented from a source level. - -jay -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknWNWoACgkQ2upbWsB4UtHjHwCdHLiBJmadqPQwXMNrzuJ+Ek3K SDcAoISP6zCpzvtt88G3tIQi2qEmYXeA =/8Et -----END PGP SIGNATURE----- _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
