This repository has been archived by the owner on Sep 26, 2022. It is now read-only.
Perform android http requests in separate thread #65
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This actually helps a lot in performance. In order to build, I also needed #60 . |
|
I believe this fixes #53 as well, adding it to my list |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm currently having a problem with the HTTP plugin on Android.
Whenever I try to perform an HTTP request, it seems the javascript runtime hangs and only continues when there is a result from the HTTP plugin. This is very bad for my app because we need to perform some tasks in "background" mode and still allow the user to navigate within the app.
I've implemented a workaround for this, which is included in this PR. I am not an expert in Android development, so I am not sure whether this is the best approach (I used a simple thread).
Suggestions and other workarounds are also welcome if this PR is not appropriate.