Good to see this.... Eric, do you have an open jira for client bindings?
Thanks mahadev On 4/21/10 8:32 PM, "Eric Hauser" <ewhau...@gmail.com> wrote: > I submitted the Jute changes back as ZOOKEEPER-747. > > Regarding contrib, I'd be happy to submit the client bindings back once I do > a bit more cleanup. > > On Mon, Apr 19, 2010 at 1:11 PM, Patrick Hunt <ph...@apache.org> wrote: > >> Hi Eric, this sounds great! Please consider submitting the client binding >> back, you could start it as a contrib package (src/contrib) until things >> settle and you get some usage. We recently have been seeing interest in >> running ZK on windows servers, so having .net would be awesome. >> http://wiki.apache.org/hadoop/ZooKeeper/HowToContribute >> >> It would be nice to see the Jute support, btw this is a port of Hadoop's >> "recordio" package from a few years ago. We are actually looking to move to >> Avro at some point, I'm sure they would love to have .net support as well. >> >> Regards, >> >> Patrick >> >> >> On 04/15/2010 05:55 PM, Eric Hauser wrote: >> >>> Hi, >>> >>> I've ported the Java ZK client to .NET. It's available for forking at >>> http://github.com/ewhauser/zookeeper/. It is still in very early stages, >>> but all of the client tests that I have ported complete successfully - >>> both >>> normal calls and watches are working successfully. Some things to keep in >>> mind: >>> >>> - It's not actively being used at the moment >>> - I have not had any chance to do any performance testing >>> - The API will definitely be changing. I've ported watches over as is in >>> order to get everything working, but I'll be changing that to use events >>> instead to make it more .NET-like. >>> - There are not any asynchronous methods on the ZK client API -- async >>> method calls are easy to do .NET. May add a wrapper for it at some point. >>> >>> If there is any interest in having any part of my work go back into trunk, >>> I'm happy to sign the ASF release. In particular, it would be nice if the >>> C# support I added to Jute made it back into the core code base. >>> >>>
