I had thought about this, but my understanding is that jetty can only serve static content from a pre-designated set of paths. This means each person would have to configure jetty for each additional project they want to test locally, which would add a fairly big hurdle to developers only comfortable with JS.
The target audience here is scripters who wish to test their gadgets locally, and it seems like requiring them to configure jetty would be a big deterrent. On Wed, Dec 10, 2008 at 6:38 PM, <[EMAIL PROTECTED]> wrote: > Why not just configure jetty to serve static files? > > > http://codereview.appspot.com/10269 >
