Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Selector question

See commit e6e49bdc85

On 25 May 2018 at 07:48, Greg Wilkins <gregw@xxxxxxxxxxx> wrote:


that javadoc is indeed out of date.

We now allow Callback instances to use the Invocable interface to declare if they are blocking or non-blocking, with blocking being assumed.  So there are no limits on what can be done... other than if a callback declares itself to be non-blocking, then it should not block no linger too long.

I will remove that old documentation.


On 25 May 2018 at 01:01, Josh Spiegel <joshlakewg@xxxxxxxxx> wrote:

In the documentation ServerConnector, I see the following text:

It is the selector thread that will call the Callback instances passed in the EndPoint.fillInterested(Callback) or EndPoint.write(Callback, java.nio.ByteBuffer...) methods. It is expected that these callbacks may do some non-blocking IO work, but will always dispatch to the Executor service any blocking, long running or application tasks.

But I also found this blog that made it sound like maybe this is no longer the case?

Can anybody clarify?  Specifically, I would like to know if onFillable() will be run by a selector for ServerConnector/AbstractConnection.  And if not, is it ok to do blocking operations in onFillable()?


jetty-users mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit



Back to the top