Force Xnet Server to flush it's client cache

[defrag]

My xnet server lives on a server that sleeps. Xlobby is running as a service on the server (this works great by the way and seems 100% stable).

If the server wakes from S3, it retains the connection to a fat client that may not be awake, this then blocks ALL clients from connecting. Fat clients get a .net sockets error and will not connect.

Now I realise that this is not going to be a common setup for most people, but for me it's the best way to have a centralised xlobby running on Windows Server 2003 serving out to fat and thin clients.

Anyway, it would be handy to be able to somehow get the server xlobby to flush it's connections (or at least test for "real" connections).

If this is already possible, slap me and tell me what I should be doing

[wesblack]

I will speak to Steven about this and let you know the outcome.







Wes Black \ Calrad

[defrag]

Thanks Wes