I would be "matt", in this case.
You are right, B_M....I don't fully understand how it works... I'm not a developer. I just call it like I see it.
The guess that I've "never counted how long the pause is" would be wrong.
The other guess that I have "never lost a slot" would also be wrong.
And I can prove it.
I made it a point before posting to make proof of "matt's" statements. I made screen recordings of the very things noted in that small hub. In the screen recordings, there are both 2-3 second pauses between segments (according to the client) , and a longer pause that lead to a slot loss. I welcome and encourage the developers to view my .avi screen recordings of the things mentioned at the top of this thread.
Before I get deemed as a trasher of the client, I want to point out that I currently run a 4 yr old hub, I know how to forward ports (otherwise, my hub wouldn't run), and I am not a noob. I am a veteran user of PW, Strong, and CrZ. The whole reason this thing came up is... none of the other clients ever exhibited the behavior outlined above. Apex has. That's it. I'm not here to bash or tarnish something that has obviously been carefully worked. I care about your effort, therefore, I speak.
Hopefully one of the dev. team will glance once again at this thread, and be curious enough to inquire with me about the screen recordings that I took the time and effort to make for the benefit of all. Most of all, I'd like Big Muscle to see the recordings... just so a guy I respect BIGtime doesn't think "matt" is an idiot. ;-)