AltME: R3 Protocols

Messages

Luis: 23:13Only change line 583 of ypur code pointing it to another ftp host . Tested without problems with Android ftp apps and same R3 code OK on Windows.
GrahamC: 23:17And did you try any other ftp host?
Luis: 23:17Nop
Luis: 23:21Only testing on www.byethost.com (free hosting)
Luis: 23:30same result on 000webhost.com. On Android only get first line: "port opened ...". No problem on Windows.
GrahamC: 23:39Which android version is this?
Luis: 23:41Android 4.3 Note II
GrahamC: 23:43Sorry, which version of Rebol3 android? Is it r3/droid or is it another version?
Luis: 23:45From Saphirion rebol/build 12-jul-2013/19:02:11
GrahamC: 23:48so, it gets to this line https://github.com/gchiu/Rebol3/blob/master/protocols/prot-ftp.r#L532 and returns a port ?

23:49All the 'read does is to kick off the awake handler

23:51it should then do the 'lookup so if you remove the comment https://github.com/gchiu/Rebol3/blob/master/protocols/prot-ftp.r#L238

23:54Sounds like from what you're saying, it's not even getting to https://github.com/gchiu/Rebol3/blob/master/protocols/prot-ftp.r#L234

Luis: 00:01Exactly
GrahamC: 00:08so, you do
cmd: open ftp://site.name
and then
wait cmd
and it just hangs?
Luis: 00:13read cmd return none but wait cmd advance to login !!
GrahamC: 00:14that's odd .. sounds like it's waiting on the wrong port then
Luis: 00:25If 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

00:26Coffe time with my wife, returning in 40 minutes....
Luis: 01:58Adding "wait 0" lines after each "read cmd" I can get the htdoc dir (sometimes hang) .
GrahamC: 02:09I'm afraid it's alpha level software