On Jan 17, 2007, at 1:41 AM, Chris Hostetter wrote:
: The number of people writing update plugins will be small
compared to
: the number of users using the external HTTP API (the URL + query
: parameters, and the relationship URL-wise between different update
: formats). My main concern is making *that* as nice and
utilitarian as
: possible, and any plugin stuff is implementation and a secondary
: concern IMO.
Agreed, but my point was that we should try to design the internal
APIs
indepently from the URL structure ... if we have a set of APIs,
it's easy to come up with a URL structure that will map well (we could
theoretically have several URL structures using different servlets)
but if
we worry too much about what hte URL should look like, we may
hamstring
the model design.
+1
web.xml allows for servlets to be mapped however desired, and
cleverly using a servlet filters could add in some other URL mapping
goodness, or in the extreme must-have-certain-URLs there is always
mod_rewrite.
I still think a microcontainer is a good way to go for solr. It's
exactly what microcontainers were designed for. While not spring-
savvy myself (but tinkered with HiveMind via Tapestry a while back),
I know enough to reiterate that its not heavy or horrible for basic
IoC which is what is being reinvented in a sense.
Erik
