retrieving data from TCP port

.. http://www.escribe.com/internet/rebol/m26710.html Hi, Francois, Assuming I understand the problem correctly, with just a minor change, you may be able to simplify things considerably. Here is the quickest version that *may* do the job: ;open a port named port port: open tcp://x.x.x.x:3221 ;let the word initial contain the sample xml initial: read %initial.xml ;cram the xml into the port ;**note that a return value is _not _ ; checked from this statement insert port initial ;assuming server is very fast, simply read the return ; (it is usually hazardous to assume anything, though) result: copy port ;close the port close port ;check returned result for a unique fragment ; suggesting success or failure either find result "</rpc-reply>" [ print "success!!" ][ print "ooh, got an error..." ] If the port times out, or you get mysterious errors, or you want safer code, then you may need to approach the problem differently, possibly use an asynchronous mode (the no-wait option) and continue polling until you receive a none (similar to what you were doing in your code). I would have to experiment to with a live example to get it to work right, but it would be something like: port: open tcp://x.x.x.x:3221 initial: read %initial.xml insert port initial result: copy "" portion: copy "" while [portion: copy port] [append result portion] close port either find result "</rpc-reply>" [ print "success!!" ][ print "ooh, got an error..." ] I *hope* that helps. It helps to have a working server to try the code against (I'm not good enough to see all the silly errors I may do on first coding :-). --Scott Jones

** Access Error: Network timeout ** Where: halt-view ** Near: result: copy port

I'll have to fire up tcpdump and see if data is really comming back in....either that or adjust the time outs. What does copy wait for before terminating/closing the port Francois

'copy wait for RST or FIN packet imo, or new data arrival. In sync mode, you exit the loop either by retrieving new data on the port, getting port closed by remote side, or receiving timeout on port ... I don't like sync mode and I use /no-wait mostly ... -pekr-

Bummer.

May not be a need to fire up tcpdump nor adjust the time outs. My program samples suffer from not being able to test a nd adjust. Of course, if you want to fire up tcpdump, then fire away! :-)

I may not be able to provide the best answer to this question. Basically copy is waiting for a none to be returned, but in my first example, it tried to read the response in one chunk, didn't receive the right signal. So copy stalls on the port. Everything stays open, and finally the network connection times out. I suspect a tcp/port-ologist could give a much better answer (in fact my dog on a bad day could probably give a better answer ;-). What we need is the no-wait refinement and loop that will catch fragments until the port finally returns a none (I have never figured out how anything can "receive" a "none"; I guess it is like the sound of one hand clapping. ;-) Try this variation: initial: read %initial.xml port: open/no-wait tcp://x.x.x.x:3221 insert port initial fragment: copy "" result: copy "" while [ wait port fragment: copy port ] [append result fragment] close port either find result "</rpc-reply>" [ print "success!!" ][ print "ooh, got an error..." ] If that doesn't work, then, yes, I would be happy to try a direct connection to a machine of your choosing. My guess is that the server might be line oriented, and that adding a /lines refinement would help. Again, just a guess... Good luck! --Scott Jones

...

Hi, Francois, So, pardon my ignorance, but do you have what you need? Hoping you do ... --Scott Jones