AltME: R3 Protocols

Messages

Rebolek: 21:39I set up the handler for the redis-port and here it's moved to the tcp-port

21:39It's probably copied from some example.

21:40From the HTTP protocol.
GrahamC: 21:42maybe
redis-port/state/awake: :port/awake
should be
redis-port/state/awake: :redis-port/awake

21:43because in our write actor, there is no 'port defined

21:43our => your

21:43just guessing now ... must have breakfast!
Rebolek: 21:43I changed the Async part of WRITE to:
            ;  --- ASYNCHRONOUS OPERATION
                unless open? redis-port [cause-error 'Access 'not-open redis-port/spec/ref]
                tcp-port: redis-port/state/tcp-port
                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
                ]

21:44And I setup tcp's awake in OPEN, but the result is still the same, it prints and then it waits.

21:44Ok, breakfast is important! :)
Rebolek: 21:49I pushed latest version to GitHub together with %async-test.r3 so ou can look at the version I'm using here.
Andreas: 22:12Do you have the console print output you get somewhere gisted?
Rebolek: 22:14just a moment...

22:15 https://gist.github.com/rebolek/5717776

22:15There's wait after "..Read 5 bytes"
Andreas: 22:23mhm
Rebolek: 22:33exactly...

GrahamC: 00:54don't know what's current but this line should be
https://github.com/rebolek/prot-redis/blob/master/prot-redis.r3#L250
tcp-port/spec/port-state: false or none
GrahamC: 00:58 https://github.com/rebolek/prot-redis/blob/master/prot-redis.r3#L431
could be
tcp-port/awake: :awake-handler
so, your example could be
rp: open redis://192.168.2.11:10
write rp [ SET asynctest true ]
wait [ rp 3 ]
Rebolek: 05:55This doesn't help, it's still stuck in the wait loop, even with the change from ASYNC-HANDLER to AWAKE-HANDLER.

Rebolek: 05:54During 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?