Maybe somebody could supply a little history about how Solr actually became
a "webapp" as opposed to a standalone web server. If the only/main/primary
reason was "because it's easier", then it may indeed be time to move on. If
it was some other reason or "requirement", then let's revisit a list of
those reasons/requirements
I have no problem with multiple packagings of Solr - embedded, webapp, raw
SolrCloud node server, etc. It might be simply the question of whether to
drop any of the Solr modes/packagings.
-- Jack Krupansky
-----Original Message-----
From: Mark Miller
Sent: Monday, May 13, 2013 5:02 AM
To: [email protected]
Subject: Re: VOTE: solr no longer webapp
On May 13, 2013, at 3:13 AM, Toke Eskildsen <[email protected]> wrote:
My impression of Solr up until 3.5 was that is was intended for
"everyone" that wanted to get started with search, big or small. It
makes sense to narrow the focus, but that should be followed by a clear
statement like "Solr is primarily intended for large scale projects but
can also be used for small scale"
Meh - I just see Solr as a search engine. People will still be able to use
for whatever scale they wish. I'm not personally going to tag line it as
intended for anything. I don't think a 'webapp' is pro small scale either.
When developing software, I have never once thought, oh, this is for small
scale stuff, I should put it in a webapp!
If I were making a search engine, whatever my intentions for it, I'd
personally never start with the idea that it's a webapp even if I used that
for the implementation.
- Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
