: I don't mind Solr being a "webapp" in Jetty. I don't recall it : constraining us or being interfering. Jetty is very customizable so we can : tweak the Jetty-Solr relationship to our liking. A webapp makes it : straightforward (no code!) for other users to add a CORS Filter in Solr or : to add another webapp if they like.
I guess i'm just out of the loop on the prevailing thinking .. at one point (around the time we stoped supporting multiple servlet containers) there was a big home that eventually we would stop being a webapp and more direclty integrate with *some* networking layer. Partly to eliminate some ofthe servlet API layer abstractions, but also to more easily do things that are hard to do in a webapp: listen on multiple ports, support multiple network protocols for intranode communcation, etc... (some of this can be wired up via jetty configs, but that's stil "jetty stuff" that solr has a hard time knowing about or dealinw with directly because of the webapp abstraction) -Hoss http://www.lucidworks.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
