Greg Wilkins

@sbordet @joakime Can you schedule a meeting to discuss this. I did not realize that you were proposing to deploy "/foo.d/static". I'm pretty much against this and I think that...

Generally I think that `jetty-web.xml` is not a great way to configure anything.... but there are certainly use-cases like this one where it is the best option. Thus no matter...

It should be easy enough to add some code that if contextHandler is null, then to ask the server for its descendants security handlers. Who calls this method and why?

We already have a mechanism that if `$JETTY_BASE/work` directory exists, then it is used for the temp directory. Note however that it has slightly different semantics as it is not...

I think it would be far simpler to just warn if /tmp is used and perhaps default to using the $JETTY_BASE/work directory ?

We are throwing a "content read fully exception".

@sbordet @lorban I think this is indeed outside of the contract. Not only do we act on a call to `HttpChannel.ChannelRequest#failed(Throwable)` after all the content is read, but we simply...

I'm not interested in anything for post analysis like spot-bugs. It is only worthwhile if the code actually fails to compile and you get warnings as you write the code....

I don't think we have time to do this before 12.1, so I'm putting this into the roadmap for later consideration.

still a good idea