Yeah, I thought Erik might reply. Beyond that, I wondered.
As to location, there are a couple of pieces here. I agree that
contrib/jruby is too generic for an app but I thought it appropriate for
the generic part of the API (that other jruby apps (?) would use).
There are two other pieces: generic rails support (for any rails app,
basically akin to ActiveRecord for Lucene) and then there's the app,
itself.
I see two ways to do this:
contrib/jruby/lib (generic juby)
/rails (rails support)
/app(s)
or
contrib/jruby (generic ruby)
/rails
/app(s)
I have a minor preference for the first; keeps everything in one place,
but ...
Rails does allow one to easily put HTTP and XML alongside each other and
emerging support for easily configured REST stuff. I haven't had time to
wrap my head around what REST means for Lucene. But I'm hoping to. Since
I'm not smart enough to get all this in my head at one time, I've been
working very incrementally, learning each piece as I try something. So
it's far from complete.
I did look briefly at the solrb API when Erik mentioned it a little
while ago. There's some overlap. I think (though this changes by the
hour) that solrb is more akin to the rails/activerecord level of
abstraction than the lucene index level. Though who knows? And I'm
interested in both. While the application-enablement is a big part, to
start with I'm interested in looking at the index guts. In my dreams,
I'd like to be able to examine posting lists, payloads when they happen
...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
