Things have been very quiet down here and hectic everywhere else. As a proof that this is no lame excuse,
my first Rails patch was just committed into the trunk.
For the record, it addresses an issue in ActiveResource which could not locate resources defined
in nested modules.
I've been using ARes a lot in my current project
in which I've built a rich client-side API packaged into a Rails plugin. To be honest, I'm into a love-hate relationship with ARes and things were not as smooth as initially advertised.
I've experienced some severe hiccups with nested resources, inflected collection names, attributes vs prefix hashes and some nasty XML (un)marshalling oddities. If I find some time, I will document here the problems I encountered during this wild ride...
Even though it has given me some serious headaches, I still think this REST approach is better than dealing with a huge black box supposedly implementing some funky flavor of SOAP.
ARes is not totally mature in its current state but the size of its code base still allows a mere mortal to dive into it and see what's happening.
If the popularity of REST services keep on rising, ARes will need some real refactoring and internal plumbing work to bring it to the same level as ActiveRecord in the ORM field.
The bottom line is: ARes is a neat library you may want to play with but you must be warned that things are not as simple as they seem and it may require some significant tweaking on both sides of the wire...