Hi everyone, I ran the event sample program on my Ubuntu linux distribution and had a question with regards to synchronous event messaging in the example.
When I set the synchronous variable to 1 enabling synchronous messaging. I notice that the event and handler lock up. The event app sends an event message and then waits for an empty response (from the handler) using the soap_recv_empty_response function. The handler responds appropriately with an HTTP 202 acknowledge. This message only has a header and no body. The event app receives the HTTP 202 and one would think that it would be done at this point and close the socket, but instead it tries to read the message body (even though there isn't one). The event app is now blocked on the socket and the thread on the handler side is also blocked on the socket until it times out. This seems to be a bug to me. I would think that the event app upon receiving the HTTP 202 response message knows that it is done and would proceed to close the socket and continue on it's merry way. Is this a problem or is there something I overlooked? Thanks for any help or suggestions. Dominique
