Hi Seeker,

>I just installed Norton Internet Security (overgrown AtGuard) and watched in the statistics as XoloX connected to the internet trying 60 hosts at once! XoloX should not be trying to connect to more hosts than it wants to have total.

XoloX tries to connect to 40 hosts at once.
As soon as 2 active hosts are found, this maximum amount of trying host will drop to 20 automaticly.
In a stable condition (after 30 sec) xolox will have from 2 to 5 connections. We need this fast trying procedure, to kill some waiting time. At the present state, no running connections are killed by XoloX !!!

>I've noticed is that XoloX will sometimes continues to download a paused segment. I've seen the bug several times but can't reproduce it at will, probably due to my very limited bandwidth. Either it doesn't always abort all currenty active segments, or it doens't buffer all current attempted segments then starts downloading if it connects after the user pauses the job.

Good point. When you pause the job, all active connections are killed and no new connections are started. It could be that an incoming push some time later is still being assigned (after pause). We will check that out.

>One other thing... I see XoloX listening on a random UDP port on startup, and it always says it's sent 4 bytes out. What's this for?

At startup
-> XoloX requests a webpage.
-> Starts the server socket.
-> Initializes the initial outgoing connections.

That's strange.

Could you read the pakkage ?


__________________