Because of the:
lappend ::srvData(clientResponse) $msg
on the server side, I'm not getting consistent return data. Depending on the command I issue, I will get just data back e.g. "test" or lists e.g. "{test1 test2}".
So I give up. I don't think it's worth it. The server should be improved to...
I could make that mod to the server. I will try it to see if it works for "read". I think it would be cleaner than the start/end tags.
Thanks for that!
-Brad
Using a read locks up if I leave it open ended.
If I tell it to read a small number of bytes (less than what's in the buffer), I do get the data in chunks of that size. It then locks up on the last chunk since it's (probably) trying to read more than is available. See next paragraph.
If I tell...
I tried that before and it hung. But I'm getting better at this so I'll go try again.
In the mean time I did find something similar to what I was asking about.
http://www.tek-tips.com/viewthread.cfm?qid=772165
I'm doing pretty much the same thing. But I am hacking in the "start" and "end"...
Hi Bong,
Yes I tried that. When I use -translation binary, my rx handler never pops. I changed the buffering from -line to -none to -full and the rx handler just never gets called.
I have a hack here that does what I want it to do. I hack in a prefix and suffix on the response on the socket...
Hi all,
I am interfacing two Tcl apps. The server app opens a socket. I can send commands to it and get responses. The responses are multi-line. My client receive socket handler only gets the response line by line (no matter how many different fconfigure combinations I try.)
What I'd like to...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.