Click here to Skip to main content
15,891,529 members
Please Sign up or sign in to vote.
5.00/5 (2 votes)
See more:
Hi,
i have created a wcf service using wshttpduplex binding, i wanted to check (if the client is connected or not) before calling him back, i have googled alot for the solution and worked on most suggested solution (timeoutexception). this seems to work but the issue is when i close the client test app without proper disconnecting and sends callback to the dead client the service callbacks successfully two or three times to the disconnected client and then afterwords throw the timeoutexception... i could not find out the reason; why the exception is not thrown after the first attempt to callback the client after client is disconnected

Does anyone know the solution to this?
Posted

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900