New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider adding a progress listener for Callback #26
Comments
That's a good idea. I'll start implementing it once I have some time. |
👍 |
I've done basically this on my async_progress branch: https://github.com/tcoxon/unirest-java/tree/async_progress I won't submit a pull request because it's a mega hack and the design needs some real thought. But if you urgently need this feature, you might find it useful. |
@tcoxon Since you have already built something working, if you would considering polishing a little bit I can accept a pull request and distribute it into the next release. |
When are you planning to make your next release? I'm on a very tight schedule at the moment. |
In a couple of weeks. This is a feature that it would be great to have. |
An AbstractCallback class is provided if the extra method is undesirable.
An AbstractCallback class is provided if the extra method is undesirable.
Hello there. Any news about this? |
Such a feature would be incredibly useful right now. |
Still need this, waitin' 2 years for this feature 😄 |
Would be nice to have this. |
Would be nice to have this, even still in 2017. 😄 |
After years of this issue was raised... I'm currently looking into adding this feature to the fork I have. Although is a nice thing to have, I see some caveats with it, like:
|
make it possible to completely re-init unirest back to original state
Complete in the release which should be in mvn central shortly: The monitor gets invokes separately for each file and field (inputstreams lack a file name unless explicitly given one. Also on inputstreams the total bytes is a guestimate.
|
One thing that would make this library even better is to add a simple progress callback that updates as a request is made. For POST/PUT/PATCH etc it would be great for this to monitor upload progress, and for GET/DELETE etc it would be great for download progress. Thoughts? This is another side note, but it would be nice to include a default callback class that provides stubbed implementations of the callback interface for those who don't wish to provide functionality for some of the methods.
The text was updated successfully, but these errors were encountered: