| Re: [che-dev] Outbound HTTP requests in Che server-side |
|
Hi, Please allow me to clarify. My intention is not to have a better way for conveniently sending/retrieving JSON data, but rather to manage the requests themselves regardless of whether
JSONs are being sent/retrieved. HttpJsonHelper itself is effectively many tiny wrappers this sink into a single function that sends a general request and receives its response – this internal function is the place I am discussing here. Having a common code
for HTTP requests that is reused by that core function inside HttpJsonHelper will solve the issues I described earlier. thank you From: che-dev-bounces@xxxxxxxxxxx [mailto:che-dev-bounces@xxxxxxxxxxx]
On Behalf Of Yevhenii Voevodin > Still, it does not allow intervening the request lifecycle which is the main point of my message We tried to build conceptually the same thing as HttpJsonHelper, so it doesn't provide methods for appropriate request managing e.g. you cant set headers
or use body different from JsonSerializable. I think that if you want to get content different from json or you don't want to use authentication header, then you don't need HttpJsonRequest, or it won't
be JSON request any more. We planned to use JAX-RS Client API in the future to cover the use-cases which you discussed. > Is this planned to replace the scattered code the copies HttpJsonHelper Yes the plan is replace usage of HttpJsonHelper and deprecate it. On Wed, Dec 9, 2015 at 3:55 PM, Sharafy, Tareq <tareq.sharafy@xxxxxxx> wrote:
|