Brandon <blanu at uts.cc.utexas.edu> writes: > The API should block on request. That's why we have threading. I certainly > don't want to have to do a request and then keep checking to see if the > request has come in yet. > > I don't see why you'd want to make requests non-blocking. I'm using the > blocking request right now and have a perfectly nice NNTP gateway server > which never waits for requests. It updates its cache of messages in the > background through the beauty of launching a new thread for each request.
I agree with Brandon. Non-blocking IO is for environments where threading is either not available or comes with a significant performance hit. Both Python and Java show a clear preference for blocking IO in their base libraries, for example. It might be nice to provide a non-blocking function as well, but blocking IO should definitely be the first priority. _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
