I experienced problems during intensive testing with WIPlib 1.10 ( OS 6.61 ) in the following two scenarios.
The IP libary will behave strange sometimes (!!!) when the connection is closed abnormally due to the server side ( problem experienced during ISP problems). The problem could be in our code as well but we cannot find the sulotion yet.
When a new parallel socket is created with a large send buffer (32K) and the wip_close() function called on this socket under heavy traffic load, it could ( not always!!!) hang the IP libary. Naturally the other tcp socket is “hanged” in this case. Just imagine you press the PAUSE button on IP libary, no traffic, no events, no error codes.
Has anyone also experienced this two problems?