On the first topic: yeah, if we ever get to a world where we support multiple ports, then we'll have to have some way of giving a name or identifier to each host/port connector object, and then all of the add-* functions will need to take that as an argument so that we know which one to register a handler with.  In that world, we probably *could* grab the SSLContextFactory from the connector object and get rid of the atom.

As for the performance stuff, I agree that we could probably override something else in the ProxyServlet and cache the SSLContextFactory in a local var so we wouldn't have to dereference the atom on each request.  IMO from some simple tests the difference in performance for reading an atom vs a var isn't big enough to necessarily warrant that until we actually see it being a bottleneck in practice.  It's a good suggestion, though--and something I had been thinking about a little myself--so I'm happy to continue considering it if you think it's worth it.