Handling of driver protocol extensions in cvs

[Philip Langdale]

Hi all,

I'm in the process of putting together a protocol extension
for the vmware driver and I wanted to ask what the intended
practice for organising such code is? Should I create a proto
module for the headers which the driver would then depend
on, and then a lib module for the client side bindings, as
if it was a fullscale extension? Or is there some other
preferred mechanism?

--phil