Jeevanandam M.

Results 156 comments of Jeevanandam M.

@WSZ9527 Thanks for reaching out. Typically, the term "speed" is a variable factor based on consumer use cases and data. It will be helpful for analyzes/investgation; if could provide the...

@ruinshe I think it would be best to add the dry run option in the Request object. Having a flag in the request to drop the outgoing request. E.g. `client.R().DoDryRun()`...

@ruinshe Thanks, no worries. I will take it up later.

@lrita has a point. Technically custom transport could be used with user code to achieve this. For now I will put this in the backlog.

@ruinshe Do you mind sharing the code what you did? so that we can evaluate to include in the resty lib or not? If it's trivial, we can add it...

@bynov Can you please give me a test case to reproduce it?

@janekolszak Thanks for bringing up your thoughts. I'm not sure how it will benefit to Resty users in a practical use case. Are you trying to say client-side load balancing?

@janekolszak Thanks, I see a use case. However, I'm not sure about how much this feature going to helpful to the broader audience. I will keep this open, will implement...

@lggomez I believe you're referring to response middlewares correct? If so what is the behavior you're trying to propose, do you mind showcasing via PR?

@lggomez You're welcome, it was a config issue with Travis build. Resty's middleware behavior (typically it should) will halt the execution at middleware which had an error regardless of internal...