Hi Allen,
I read your proposal and it looks interesting. Rails scaling was a
very hot topic in the community around last year I think. Apparently
twitter was having problems scaling with a single database, but a
quick solution was found (I think that it was a 75 lines of code
plugin). I don't know
Thanks for the suggestion Allen. Considering the scalability of this
solution, I'm thinking on use starling to handle the asynchronous
calls. Starling by itself is a perfectly scalable solution that allows
you to add separated servers to handle asynchronous messages. My
plugin should provide an ea
Hello,
This is the second proposal that I submitted to GSoC. Please feel free
to leave any comments on it.
Thank you.
Abstract:
Currently there is no easy way of communicating two Rails
hallenge might be
how to read the routes.rb file. I would need to investigate about how
routes work internally in rails.
On Apr 2, 10:03 am, Allen wrote:
> Hi carlosk,
>
> I really like the idea of being able to expose an API of REST services
> automatically. Can you post your proposal here?
Hello,
I submitted a proposal for the GSoC about adding a discovery file for
ActiveResource. This discovery file will allow developers to explore
(through an API) the resources that are available on a REST service. I
will also add a set of rake tasks for adding automatically generating
the REST c
