AltME: R3 Protocols

Messages

Wednesday 5th June, 2013

GrahamC

21:10connect [
;           send-redis-request event/port
            write event/port event/port/locals
        ]
Doing two consecutive writes?

Rebolek

21:10No, the first one is commented.

GrahamC

21:10oh ...

Rebolek

21:11It's bit messy...

GrahamC

21:12yeah ..

you have

port: event/port

but then still do write event/port

Rebolek

21:12yes, but it shouldn't be problem, no? It's copypasted from two different versions...

GrahamC

21:13It looks good to me .. but I only just woke up

Rebolek

21:14It prints "Read 5 bytes" and then waits until timeout. [Return true] is there so I guess it should work. But it doesn't :/

GrahamC

21:15why are you not using the port returned by 'open?

Rebolek

21:15you mean like [rp: open rp]  ?

21:16I copied that code from the example on rebol.net

GrahamC

21:17well, here https://github.com/rebolek/prot-redis/blob/master/prot-redis.r3#L402

you return the newly opened port .. so I thought you'd use it ?

Andreas

21:20Bolek, you don't install an awake handler on the TCP subport.

21:21In line 400, you explicitly clear the awake handler on the TCP subport:
https://github.com/rebolek/prot-redis/blob/master/prot-redis.r3#L400

21:21So I don't think the awake handler you install on the Redis parent port (the example you pasted above) will be called at all.

GrahamC

21:22so, you need to get the port returned by open and install the async handler on that

Andreas

21:22Right.

GrahamC

21:23I was getting there ... heh

Rebolek

21:24But  READ in ASYNC-HANDLER gets called.

Andreas

21:25Are you absolutely sure about that?

Rebolek

21:25I changed the line 400 to [tcp-port/awake: :redis-port/awake] and it's still the same.

Last message posted 489 weeks ago.