Hope I''m asking a valid question, but I would like to provide a Ruby/ Rails client library for a web service I''ve created. I''m not a proficient Ruby/Rails developer so I''m not even certain the metaphor of "client library" applies. I have programmatic familiarity with supplying the appropriate bits for Java, PHP, Microsoft, etc. I want to support Ruby/Rails development against our service, but am not quite sure what to provide or supply. If someone could point me in the right direction (or to the right documentation), I''d be greatly appreciative. cheers, jro --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Hi Jeff In the rails world, we talk about plugins. You could just google for ''rails plugins'' . On Oct 12, 6:03 am, JeffRo <jeff.rodenb...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Hope I''m asking a valid question, but I would like to provide a Ruby/ > Rails client library for a web service I''ve created. I''m not a > proficient Ruby/Rails developer so I''m not even certain the metaphor > of "client library" applies. > > I have programmatic familiarity with supplying the appropriate bits > for Java, PHP, Microsoft, etc. I want to support Ruby/Rails > development against our service, but am not quite sure what to provide > or supply. > > If someone could point me in the right direction (or to the right > documentation), I''d be greatly appreciative. > > cheers, > jro--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
On 10/11/07, JeffRo <jeff.rodenburg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > Hope I''m asking a valid question, but I would like to provide a Ruby/ > Rails client library for a web service I''ve created. I''m not a > proficient Ruby/Rails developer so I''m not even certain the metaphor > of "client library" applies. > > I have programmatic familiarity with supplying the appropriate bits > for Java, PHP, Microsoft, etc. I want to support Ruby/Rails > development against our service, but am not quite sure what to provide > or supply. > > If someone could point me in the right direction (or to the right > documentation), I''d be greatly appreciative.Rails is a server application framework. Ruby is a general purpose scripting language. Rails is written in Ruby. Your client library should provide an API to your service. It should be written in Ruby and packaged as a gem. Gems (rubygems.org) are the standard packaging system now. RubyForge (rubyforge.org) is the place to host development of your client library. If you publish a gem at your RubyForge project, any Ruby installation can install it with a simple "gem install jeff-lib". There is quite a bit in the Ruby standard library and in 3rd party gems to support all kinds of networking and web service protocols, so you want to leverage those of course. Rails plugins are a different beast. They are extensions to the Rails framework, to assist with development of Rails applications. You don''t want to lock yourself into a plugin; however, if Rails server applications need to interact with your service as a client, you might have a plugin that provides some "glue" between Rails and your client lib gem. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Bob - Thanks for your comments, this is super helpful. Are there any suggested gems worth looking at for guidance? Maybe a gem for working with Amazon web services, as an example? On Oct 12, 6:20 am, "Bob Showalter" <showa...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> On 10/11/07, JeffRo <jeff.rodenb...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > Hope I''m asking a valid question, but I would like to provide a Ruby/ > > Rails client library for a web service I''ve created. I''m not a > > proficient Ruby/Rails developer so I''m not even certain the metaphor > > of "client library" applies. > > > I have programmatic familiarity with supplying the appropriate bits > > for Java, PHP, Microsoft, etc. I want to support Ruby/Rails > > development against our service, but am not quite sure what to provide > > or supply. > > > If someone could point me in the right direction (or to the right > > documentation), I''d be greatly appreciative. > > Rails is a server application framework. Ruby is a general purpose > scripting language. Rails is written in Ruby. > > Your client library should provide an API to your service. It should > be written in Ruby and packaged as a gem. Gems (rubygems.org) are the > standard packaging system now. RubyForge (rubyforge.org) is the place > to host development of your client library. If you publish a gem at > your RubyForge project, any Ruby installation can install it with a > simple "gem install jeff-lib". There is quite a bit in the Ruby > standard library and in 3rd party gems to support all kinds of > networking and web service protocols, so you want to leverage those of > course. > > Rails plugins are a different beast. They are extensions to the Rails > framework, to assist with development of Rails applications. You don''t > want to lock yourself into a plugin; however, if Rails server > applications need to interact with your service as a client, you might > have a plugin that provides some "glue" between Rails and your client > lib gem.--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---