-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
HttpInput may skip setting fill interest #5692
Merged
sbordet
merged 4 commits into
jetty-10.0.x
from
jetty-10.0.x-5691-httpinput_skip_fill_interest
Nov 23, 2020
Merged
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
8edb5cf
Issue #5691 - HttpInput may skip setting fill interest.
sbordet 4654335
Fixes #5691 - HttpInput may skip setting fill interest.
sbordet a2c0818
Merged branch 'jetty-10.0.x' into 'jetty-10.0.x-5691-httpinput_skip_f…
sbordet 1ac0af4
Fixes #5691 - HttpInput may skip setting fill interest.
sbordet File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this method is correct, but I think it would read better as:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gregw Regarding your TODO, yes you must call
onContentAdded
in this case. Imagine a servlet calling isReady twice. The first timefalse
is returned but the 2nd timetrue
is returned. If you do not callonContentAdded
to switch the state to READY, it'll be stuck at UNREADY which will cause havoc.Oh, and I also added in the javadoc of
ContentProducer.isReady
that After this call, state can be either of UNREADY or READY as the state cannot be left IDLE after isReady is called.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lorban But if isReady() has returned false, then regardless of it being called another time there is a scheduling action that will take place behind the scenes to make sure onDataAvailable is called when data becomes available. Surely it is that action that will call
onContentAdded
. Can you write a test case to demonstrate why this call is needed?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've opened #5704 to track this.