Shareaza

If adding security rules is going to be computationally intensive, might I suggest at least:

1. Doing it in a separate thread from the one that makes the UI responsive, and

2. Giving that thread a lowered priority?

Basically, the same as is already the case for hashing.

That's a design flaw in Shareaza. In fact, what we need would be a lockless and separated GUI, this means that everything else should be performed in a thread separated from the one executing / displaying the GUI and there should be buffers allowing the GUI to access data to display without being forced to wait until an other part of the application has stopped working on it respectively modifying it.