Webclient implementation (#1205)

[Verdent]

More tests and updated examples will be added after the merge probably.

[romain-grecourt]

The names ClientXXX feel too generic and not specific to WebClient or HTTP client. Maybe this is something that should be discussed with the team.

[romain-grecourt]

Thinking-out-loud.

I don't know if having a configuration for request/response specific readers/writers is really useful.
Instead you could expose the context from request/response and let the user add these manually for each request/response.

If we think there is a need to have HTTP client specific readers/writers for all client request/response, then maybe we should consider updating MediaSupport, MessageBodyReaderContext and MessageBodyWriterContext to support creating a parented MediaSupport.

This way you would only need to pass-in a MediaSupport instance to RequestConfiguration.

[Verdent]

Ah this is great you are mentioning this. I have a note to create issue for that. I think that having builder on MediaSupport which allows you to insert explicit parent, would be great for my usecase. I didn't added yet, because I wanted to talk to you about it before.

In case of the exposing of context, I do not think that is what we should do.

The reason why I opted for specific readers/writers for each request/response is, that it allows you to have control over entity handling. Basically you can have two or more ways how to handle specific entity type in your code and this helps you to achieve this without interfering with other request where it is not desirable.

[romain-grecourt]

There should be a parented context dedicated to each request, that would be symmetrical to how it's done in the webserver currently. We can talk more about this when you have some time.

[tomas-langer]

LGTM