AltME: R3 Protocols


From Saphirion  rebol/build 12-jul-2013/19:02:11
All the 'read does is to kick off the awake handler
it should then do the 'lookup so if you remove the comment
Sounds like from what you're saying, it's not even getting to

so, you do
cmd: open
and then
wait cmd
and it just hangs?
read cmd return none but wait cmd advance to login  !!
that's odd .. sounds like it's waiting on the wrong port then
If change "read cmd"  by "wait cmd" The last lines are:
C:  PASS mypsw
===Client event: wrote
wrote to port, now read from it
=== Client event: read
Coffe time with my wife, returning in 40 minutes....
Adding  "wait 0" lines  after each "read cmd"  I can get the htdoc dir (sometimes hang) .
I'm afraid it's alpha level software
The 'read should be doing the 'wait on the correct port
that it's not is odd ...
especially if it works on other platforms
Apparently sometimes hangs for some seconds, finally reach the end.
Is good for me.
Thanks !
I believe this is where I got the prot-ftp.r script originally:
Should be changed...
Never mind that links to same version...

Not sure if this it the case but in current R3 you have to wait on the port that operates on the real connection (usually tcp scheme). If you wait on the 'topmost' port used by some higher-level scheme the real 'connection port' will be awaken but not the 'topmost' one.
To solve this annoyance, we probably need to introduce new field to the port object (like port/parent-port) using which the AWAKE handler can find the top-most port easily and resolve correctly waiting on higher-level scheme wrappers.
I'd like to use the term socket to indicate the real tcp-level port to ease the terminology confusion here.  And yes, the ftp protocol does do a wait on the socket.  It works fine in other OS, just not Android according to Luis' tests.

Last message posted 185 weeks ago.