I do not think it makes sense to make the web server configurable. Mostly because there's no real problem in running an HTTP service internally based on Netty while you run your own HTTP service based on something else like Tomcat. What's the problem?
On Wed, Feb 18, 2015 at 3:14 AM, Niranda Perera <niranda.per...@gmail.com> wrote: > Hi Sean, > The main issue we have is, running two web servers in a single product. we > think it would not be an elegant solution. > > Could you please point me to the main areas where jetty server is tightly > coupled or extension points where I could plug tomcat instead of jetty? > If successful I could contribute it to the spark project. :-) > > cheers > > > > On Mon, Feb 16, 2015 at 4:51 PM, Sean Owen <so...@cloudera.com> wrote: >> >> There's no particular reason you have to remove the embedded Jetty >> server, right? it doesn't prevent you from using it inside another app >> that happens to run in Tomcat. You won't be able to switch it out >> without rewriting a fair bit of code, no, but you don't need to. >> >> On Mon, Feb 16, 2015 at 5:08 AM, Niranda Perera >> <niranda.per...@gmail.com> wrote: >> > Hi, >> > >> > We are thinking of integrating Spark server inside a product. Our >> > current >> > product uses Tomcat as its webserver. >> > >> > Is it possible to switch the Jetty webserver in Spark to Tomcat >> > off-the-shelf? >> > >> > Cheers >> > >> > -- >> > Niranda > > > > > -- > Niranda --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org For additional commands, e-mail: dev-h...@spark.apache.org
