Hi,

Just a testimony here, as I stumble upon this thread.
Two years ago, my team and I worked on a complex back-office for a
client : a modular sales and customer management system, dealing with
offers, sales, payment, hotline, archive of communications with the
customer. We did it with Rails and we had about 15 different
applications interconnected with webservices. We had to deal with
shared authentication, intranet accounts, rights management, sending
Objects between applications (but with different attributes, depending
on who is asking). A front-end allowed to search, edit and create a
lot of things, and more than often a hotliner action on the frontend
could trigger 10 applications in the back before getting the final
result. To do this we used ActiveRessource.

Unfortunately we didn't take the time to give feedbacks to the Rails
community about this project, but here are some bulletpoints :
- we had a very hard time finding solutions to our problems on the
internet. It seems that very, very few people are using
ActiveRessource and Rails to construct complex systems.
- If we let aside all the observations like "You should have used Java
instead" that we received from some externals, I should point out that
ActiveRessource has been pretty disappointing, and we could clearly
see how far it is from the rest of Rails features in term of quality.
We felt that only few people actually use it.
- we had to patch for some issues and we wrote several plug-ins to
help us communicate between apps. We had to code it quick and we now
that the quality level of our coding was not enough to submit these
things to the Rails community. In a sense we lacked confidence. But
the thing is : ActiveRessource is far from being enough to do serious
work with several Rails apps, it's still experimental in my opinion.
And since my project two years ago, it has not evolved a lot.

I think that it would be a good move to make it an external gem, and
if a core-team member or a serious Rails committer takes the lead, I'm
ready to help and to rework on some patches we did.

Pierre

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-core?hl=en.

Reply via email to