Hi folks. My name is Kevin Ballard and I'm an intern at Rapleaf. Among
other things, I have been tasked with "rubifying" the thrift ruby
libraries. I took a look at them, and they look like they were written
by a Java developer. Rubifying the existing libraries would be very
difficult.
What I want to do is completely rip out the old libraries and re-write
them in the Ruby way. This should clean up the API and make things a
lot easier for ruby developers to understand. The biggest issue here
is, of course, that the API will be changing, and changing in ways
that means that non-ruby developers won't be able to easily draw
parallels between their code and the ruby code. I view this as a
necessary sacrifice. I believe it should be possible to write a
'thrift/old' library that would wrap the new libraries in the old API
for existing code, but I also think that creating a new API now is
very important to do before the old one is so entrenched that we can't
change it.
I also want to fully spec out this new code and package it up as a
gem, so anybody who wants to write a client can simply `gem install
thrift` and be up and running.
Are there any objections, suggestions, or questions here? If not, how
should I go about working? Is there a git repository somewhere? Should
I maybe just create a new git repo on github.com for just the ruby
libraries and work there, where everyone can see, and then submit it
back for inclusion in the main project when it's done? Or are there
other suggestions?
-Kevin Ballard
--
Kevin Ballard
[EMAIL PROTECTED]
