> I wonder if starting from the top down would be a good way to
approach this
> discussion. Like talking about the public API then talk about the code
> underneath to support it, then refactoring etc.. So even before
discussing
> something request/response "placeholder" classes problem, I'll just
express
> some of the API things that I've always wanted and/or disliked ;)
+1. Let's start from request/response "placeholder" classes.
> * document field method accessors
> doc.id (or at least doc[:id])
> # instead of
> doc['id']
+1.
> * ability to pass in arbitrary query fields directly to solr without
> worrying about solr-ruby raising an error
Why do you need this ability?
Other than those above, I think you show good things up
to start our discussion and they are interesting.
I'd like to get comments/feedbacks from my associate (rubyist).
Cheers,
Koji
