Re: SOAP - Problem with separate threads

2007-10-26 Thread Mark Smith
Dave, I'm not sure how useful my own code for this would be, as it makes quite a few interlinked function calls, but the gist is that it builds the request and puts it (urlEncoded) into a temp file (see docs for 'the tempName'), builds up a command string for curl, does the post, gets the r

Re: SOAP - Problem with separate threads

2007-10-26 Thread Dave
Hi, Yes, I use the post command. Will curil work on Mac and Windows? I took a look at curl, but I can't figure how to use it to send and receive a soap command. This the code I use: -- -- Post the Request -- try set the HTTPHeaders to myHTTPHeader --

Re: SOAP - Problem with separate threads

2007-10-26 Thread Mark Smith
I imagine that you're POSTing the SOAP calls to the server, so you could try using curl shell commands for the POSTs - that way, your SendSoapCommands will not return until they have got a response. Best, Mark On 26 Oct 2007, at 18:49, Dave wrote: So what I want is for SendSoapCommandX() t

Re: SOAP - Problem with separate threads

2007-10-26 Thread Dave
Hi, I've been working on this, but I still can't get it to work how I want it to. I have a series of SOAP requests that much be executed in sequence. The data received from sending one command is used as a parameter to the next. As an example, here is the following Pseudo code. put Send

Re: SOAP - Problem with separate threads

2007-10-24 Thread Andre Garzia
Hello Dave, you can't use wait. Even wait with messages. If you use waits and for some reason you have nested wait blocks, you need to unblock them from the inner to the outer or they will still be blocked. With the nature of your software where you have two streams causing the waits - the server

Re: SOAP - Problem with separate threads

2007-10-24 Thread Dave
Hi, Just thought of something! I use the post command to send the request to the server. If I get the "error previous request not completed" error, couldn't I just check for for this and re-issue the command after a wait? The code would read something like this: --

Re: SOAP - Problem with separate threads

2007-10-24 Thread Dave
Hi Andre, Thanks a lot for the detailed response. I'd actually thought of using a queue to hold the requests, it seems like a better approach anyway, however I didn't do it like that because I couldn't figure out how to return the results from the request. In my SOAP library, all requests

Re: SOAP - Problem with separate threads

2007-10-23 Thread Andre Garzia
Dave, never, ever, use a wait command while network routines may be working. The wait call will wreck them. If the problem is entering a race condition, like, when one call is being placed, the other can't work. This happens because libURL will queue requests to the same server, so if you call the

SOAP - Problem with separate threads

2007-10-23 Thread Dave
Hi All, I have implemented some SOAP calls and it all works fine, except that I have need to send Poll to the server every so often. When the timer goes off, it makes a call to the SOAP Library, this too works fine unless you do something in the user window that causes another SOAP librar