AltME: R3 Protocols
Wednesday 5th June, 2013
our => your
just guessing now ... must have breakfast!
I changed the Async part of WRITE to:
; --- ASYNCHRONOUS OPERATION
unless open? redis-port [cause-error 'Access 'not-open redis-port/spec/ref]
either probe tcp-port/spec/port-state = 'ready [
write tcp-port to binary! make-bulk-request data
tcp-port/locals: to binary! make-bulk-request data
And I setup tcp's awake in OPEN, but the result is still the same, it prints and then it waits.
Ok, breakfast is important! :)
I pushed latest version to GitHub together with %async-test.r3 so ou can look at the version I'm using here.
Do you have the console print output you get somewhere gisted?
just a moment...
There's wait after "..Read 5 bytes"
Thursday 6th June, 2013
don't know what's current but this line should be
tcp-port/spec/port-state: false or none
so, your example could be
write rp [ SET asynctest true ]
wait [ rp 3 ]
This doesn't help, it's still stuck in the wait loop, even with the change from ASYNC-HANDLER to AWAKE-HANDLER.
Wednesday 12th June, 2013
During redis:// test I crashed Rebol with "#9910: unspecific" error. I'll try to isolate the problem (but I guess it needs lots of reads and writes on TCP port). Has anybody seens this error before?
I've seen unspecific errors before but never recorded which ones
Friday 31st January, 2014
How can I read multiple TCP responses to one request? When I WAIT on port, I get first response and I can see with Wireshar other responses were sent also, but how do I access hem from Rebol?
Monday 3rd February, 2014
Rebolek: I guess you need to implement your own awake handler for that.
(You might also check here for some tcp examples:
I'm writing my own awake handler for this, I just don't know how should to deal with his situation :)
Last message posted 254 weeks ago.