@tipsy if you had at least a URI object, so you can move port/host/path/queries onto it

dave: would that be a good abstraction? i thought i should limit the abstraction to response/request, since that's all i'm getting from the servlet 🤔

Well by tightening the abstraction, you make the API clearer. For instance, if you have a method called header() on the context, is that referring to the request or response?

if you have a method called header() on the context, is that referring to the request or response?

header/cookie methods is the main reason i want to create response/request inside of context

Agreed. Req/resp first would be clearest and then url on request should it need breaking down further.

http4k looks neat btw, nice work