AltME: R3 Protocols

Messages

Wednesday 5th June, 2013

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:15https://gist.github.com/rebolek/5717776

22:15There's wait after "..Read 5 bytes"

Andreas

22:23mhm

Rebolek

22:33exactly...

Thursday 6th June, 2013

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:58https://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.

Wednesday 12th June, 2013

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?

GrahamC

06:10I've seen unspecific errors before but never recorded which ones

Friday 31st January, 2014

Rebolek

21:23How 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

Cyphre

16:01Rebolek: I guess you need to implement your own awake handler for that.

16:03(You might also check here for some tcp examples: http://www.rebol.net/wiki/Port_Examples#TCP_Network_Examples)

Rebolek

16:31I'm writing my own awake handler for this, I just don't know how should to deal with his situation :)

16:31his=this

Cyphre

16:37hmm, not sure what is the problem...you should be able to handle that situation using the READ/WROTE events, no?

Last message posted 490 weeks ago.