On Thu, 13 Apr 2006 09:00:51 -0700, "Jouni Malinen" <[EMAIL PROTECTED]> wrote:
> That could be blocking an ioctl call for couple of seconds > and would be quite horrible for single threaded programs. I would say that waiting for couple of seconds in the kernel would be quite wonderful for single threaded programs, when you consider the alternative. I can guess now what your concern is, even though you failed to articulate it: a single-threaded GUI application, which cannot respond to events when blocked in getting scan results. If that's the case, we should be looking at having both blocking and non-blocking calls to fetch scan results. > [...] but what if some other program were > to request a new scan between the completion event and the attempt to > read the previous scan results.. I do not see how this is relevant. -- Pete - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
