There have been a number of users looking at the Ruby Gem for the first time and have come with many comments and suggestions.  We have been rolling in these suggestions as quickly as possible to generate a new version of the SDK.  I wanted to let everyone know the 2.0 version which has been rewritten from the ground up will be going out soon.  We are considering doing an early release and we wanted to get some feedback if this would be valuable for you.  We see the primary reason to let everyone help with the interface redesign and make the API as easy as possible to work along with giving early feedback that will let you shape the next release.

With the Ruby Gem we always encourage users to help or contribute as well.  Since version 0.5 we have been available on Rubyforge with sourcecode available in SVN.  I will be commiting to the head revision soon the new changes.  If there is enough interest creating I can also create a new pre-release build to let everyone try the new Gem.

Regards,
    Barry R.

BarryR:

If there is enough interest creating I can also create a new pre-release build to let everyone try the new Gem.

 Definitely interested in this!  I was just starting to write a simple tutorial for using nirvanix with rails on our blog since I didn't find one (which is surprising since I know lots of people who would use nirvanix with their rails sites if they knew about it).
 

 +1 as I'm sure anyone else who is not-yet-live would say, it would be great to see where you are headed, with a (non-commital) sense of how long you think it will take to get there.

as long as arjini is mentioning pet peeves around naming...

is there a reason it is 'callbackURL' and 'downloadURL' but forwardingUrl, etc. in other calls? (you windows/.NET folks and your case-insensitivity!)

andjules:

is there a reason it is 'callbackURL' and 'downloadURL' but forwardingUrl, etc. in other calls? (you windows/.NET folks and your case-insensitivity!)

Yes the forwardingUrl should be forwardingURL.  For the base library I will try to make sure it doesn't mind the case since it will be dynamic.  I will explain that more as I get closer to releasing.  The timing is always difficult because the sheer number of things we are working on.  The Ruby library has been my pet project and I like to make sure its working, error free and efficient.  I am looking forward to getting this out with some Rails examples.

arjini:

One pet peeve I hope is fixed: - method_names_like_this - ClassNamesLikeThis

The primary difference will be the similarity to the base Nirvanix calls.  We will still need to keep the existing methods in the Gem to allow for backword compatability when people upgrade.  I think the final result will be quite acceptable.

Regards,
   Barry R.