NetStumbler.org Forums - View Single Post

nikolatesla20 · 02-24-2004

Actually, it is probably more of a technical issue. I can easily see why it could cause problems.

You really want NS to be as fast as possible, in other words, to be able to pick up new AP's as soon as it sees them. Well, if it calls an external routine when it finds an AP then it has to wait for the external routine to finish (return) before it can detect another AP. So you could miss AP's because of this.

On the other hand, you could construct NS to call the external routine "asynchronously" in which case you wouldn't slow down NS. But now you run into another problem, that you could end up calling the same routine twice in a row really fast. So you still need to serialize the calls somehow. The only way to do that would be to buffer the call until it can be processed, which can be a complex undertaking.

That's why such a routine is a little more complicated than one might think.

-niko

02-24-2004	#9 (permalink)
nikolatesla20 Registered Member Join Date: Feb 2004 Posts: 27	Actually, it is probably more of a technical issue. I can easily see why it could cause problems. You really want NS to be as fast as possible, in other words, to be able to pick up new AP's as soon as it sees them. Well, if it calls an external routine when it finds an AP then it has to wait for the external routine to finish (return) before it can detect another AP. So you could miss AP's because of this. On the other hand, you could construct NS to call the external routine "asynchronously" in which case you wouldn't slow down NS. But now you run into another problem, that you could end up calling the same routine twice in a row really fast. So you still need to serialize the calls somehow. The only way to do that would be to buffer the call until it can be processed, which can be a complex undertaking. That's why such a routine is a little more complicated than one might think. -niko Last edited by nikolatesla20 : 02-24-2004 at 03:07 PM.