I don't know whether you would find listing 12.16 from ReGinA useful:

It is based on Jetty rather than com.sun.net.httpserver.HttpServer but
might provide some useful inspiration:

https://github.com/Dierk/GroovyInAction/blob/master/listings/chap12/Listing_12_16_GroovletExample.groovy

Also, I don't know whether you need a separate -m switch or whether
you could hook into the existing "listen on port (-l port)"
functionality but modify it to accept a class name.

Cheers, Paul.


On Sun, Dec 11, 2016 at 8:33 PM, Daniel Sun <realblue...@hotmail.com> wrote:
> Hi Sébastien,
>
>      The SimpleHTTPServer will be implemented with NO 3rd part library, so
> it will not impact existing production systems. In addition, it is
> recommended to be used to provide http service for convenience(such as
> testing WebRTC app). If we want to deploy our static web site, the
> SimpleHTTPServer is not recommended to be used in production :)
>
> Cheers,
> Daniel.Sun
>
>
>
> --
> View this message in context: 
> http://groovy.329449.n5.nabble.com/About-SimpleHTTPServer-tp5737191p5737205.html
> Sent from the Groovy Dev mailing list archive at Nabble.com.

Reply via email to