Hi,

I've been using Solr for some time now and made good use of the solr-ruby
library. Currently, I'm using it to power a modified version of Flare in a
project called Blacklight: http://blacklight.rubyforge.org/ - an open source
library catalog front-end.

This modified Flare is using an unmodified version of solr-ruby 0.6.0, but
I'm always so tempted to change things in the solr-ruby library to make
things easier better in Flare. So I've got some ideas on how it may be
improved upon. The issues I have with solr-ruby are related mainly to
syntactical/api things. But there are internal issues as well, like the way
solr-ruby handles creating response objects and the lack of attr readers in
the response documents. Last and certainly not least, I feel that the
library could benefit from a good cleanup and simplification. So my plan is
to head on over to the issue tracker and start plugin in some tickets. Is
this the right approach here? Does anyone else have similar ideas or
thoughts on how solr-ruby could be improved upon?

Thanks,

Matt

Reply via email to