By itself, neither of these solutions will keep track of the logged in user. If you really need this, you probably need to implement cookies, as these are necessary to keep track of the user session. Otherwise, you may be able to get away with including the basic auth credentials in each request.

I am trying to write a script that uses curl to post data to a tiny webapp that uses authlogic to provide the username/password protection. Does curl support that? I mean, I am guessing one can do a post with username and password (in raw text?) to login, but will curl and rails “remember” that it has been logged in? or do I have to supply username and password for each request that I do?

Thank You!

def test_create_via_json assert_difference(’Book.count’) do post :create, :book => { :title => “Posted via JSON”, :author => “Jason Bourne”, :isbn => “1234567890, :price => 49.95}, :format => :json end end

That makes the test agnostic of the format so you could easily do an enumeration of multiple post format’s (i.e. [:json, :html].each do |format| … :format => format}) and not have to change the test.

What do you make of this xmlrpc4r? http://www.fantasy-coders.de/ruby/xmlrpc4r/

I swear, this is my last question on this particular post. I don’t want to impose on your hobbit hospitality…

Glad you’re enjoying Rails.

Regarding XML-RPC: I never had to implement this myself in Rails, and the Rails community’s focus has definitely been on REST. ActionWebservice used to provide this functionality but was discontinued. However, it looks like someone created a fork on GitHub that works with Rails 2.1 and 2.2, supports both XML-RPC and SOAP, and includes various improvements.

ActionWebservice on Github

Blog post announcing the release

Hope this works for you.

Can you point me to some doc(s) about creating an XMLRPC server in Rails? Seems like it should be a fairly basic task, but my numerous google searches turned up nothing recent or useful…

Ruby on Rails is great…

You should be able to do something like this:

format.json { render :json => @book.to_json(:except => [:created_at, :updated_at]) }

Or the other way round, using nly:

format.json { render :json => @book.to_json(:only => [:author, :title]) }

Alternatively, you could override to_json in your Book model and have it exclude / include the necessary attributes. This may be preferable if you're rendering books to json in multiple places and don't want to duplicate the same nly / :except options everywhere.