You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 16, 2018. It is now read-only.
It should be analyzed if it makes sense to make an asynchronous version of the StAX parser similar to node.js, so reading from the stream is non-blocking by giving back execution control to the caller after some time. On the other hand, in contrast to node.js, the StAX parser could work in a separate thread, which would be less expensive to spawn one initially or on-demand as an application doesn't need to handle a lot of parallel requests, so the gains from an asynchronous StAX implementation could be minimal.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It should be analyzed if it makes sense to make an asynchronous version of the StAX parser similar to node.js, so reading from the stream is non-blocking by giving back execution control to the caller after some time. On the other hand, in contrast to node.js, the StAX parser could work in a separate thread, which would be less expensive to spawn one initially or on-demand as an application doesn't need to handle a lot of parallel requests, so the gains from an asynchronous StAX implementation could be minimal.
The text was updated successfully, but these errors were encountered: