<@U3W8YSSSV> if you had at least a URI object, so ...

# announcements

[dave]

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

[tipsy]

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 🤔

[dave]

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?

[dave]

I personally find using the IDE autocomplete for API guidance instead of java doc much easier

[tipsy]

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

[tipsy]

i thought port/host/path etc could stay in context (or in request), creating URL would make where it belongs less clear i think

[dave]

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

[tipsy]

http4k looks neat btw, nice work