Re: [Rails] What if you don't want your model to be from Active Record?

By "wrap together", I meant I would write a single function for all the functions I would use from the AWS API.

So, I should put this in the models directory, right? I want the controller to remain a "controller" with respect to rails-isms.

class MyAWSAPI

  def list_servers

    ... call to AWS API to get list of servers...

  end

  def show_server(int)

    ... call to AWS API to get info on server int ...

  end

end

On Saturday, October 12, 2013 3:49:59 PM UTC-7, Jordon Bedwell wrote:

On Sat, Oct 12, 2013 at 5:06 PM, Peter <pe...@poproj.com> wrote:
> What if you don't want your model to be tied to a database therefore not
> ActiveRecord, where do you put that model instead?

In models, because nobody said models had to be ActiveRecord because
models define behaviors but if you want the Railism that "models
should be ActiveRecord" kicked out of your models you should upgrade
to Rails 4 where now you can have ActiveRecord::Base and
ActiveModel::Model.

> I want to write a class that would wrap together the various functions from,
> let's say, the AWS API. Would I write that class and place it in the models
> directory? Or should I place it elsewhere? Thank you.

It depends on what you mean but "wrap together various functions".

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/57682901-1e89-4e35-bd21-1a399bfea0e2%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.