HEY ...im back!
*ABDUL... yes i recieve a close event if the client closes NORMALLY
but if they're terminated buy their network connection (ie crummy ISP)
then winsock dosent evoke the close event..the only way to know
is when you try to send something else to that client and get the
error.....so far!
*Edneeis, im working on a solution in line with what you have
suggested. but im going to have to clean up my code abit to
make it work in its own seperate event ( because i have unload the wsServer()
control in another err. event
*digital, I think your way is the proper way to go but i tried to evoke a
failure on my subnet and failed (ie It worked fine) so im holding out
for my friend with the crummy ISP to trip it and see whats up.
but such a remedy is obviously best left to an errorhandler
SYNOPSIS
I am coding in both into the prog. and will await subsequent crashes.
Theyre not frequent but they do happen and it annoys me to see my
server crashed when i come home!)
Stiletto.I'm working on a chat prog too.
Each client has its own winsock control
the server loads a SEPERATE control as an array at runtime upon a connection request
ie. wsServer(x) to make the control an array, when you load the control on the server form put a 'zero' in the index box!
if you need more help there are many posts here or
i can send you a cool .zip example i dnloaded from www.vbcode.com with FULL notation included!
(i dont have the link but i have the .zip vb prog)
email me...... [email protected]
Reply With Quote