Josh, 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. cheers On 25 May 2018 at 01:01, Josh Spiegel <[email protected]> wrote: > Hi, > > In the documentation ServerConnector, I see the following text: > > <quote> > 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. > </quote> > > But I also found this blog that made it sound like maybe this is no longer > the case? > https://webtide.com/avoiding-parallel-slowdown-in-jetty-9/ > > 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()? > > Thanks, > Josh > > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users > -- Greg Wilkins <[email protected]> CTO http://webtide.com
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
