Sivakatirswami wrote:
> write "RETR " & serverFile & CRLF to socket Q
> read from socket Q for 1 line
> --get data length stuff in here. . .
> read from socket transPasvIP with message "getData"
>
> on getData z
> --Where is z coming from? its not declared earlier. does the read
> --from socket automatically pass a port number?
The "...with message..." does that.
> put z into tOSocket
> --wouldn't it be the same if we just stayed with socket transPasvIP
> read from socket z with message "moreData"
> end getData
>
> on moreData g,h
> --same question. . .where are parameters/data for g and h coming from?
Same as above.
> --is this assumption correct: a read from socket with message
> --always auto generates two parameters, the socket no. and the data itself
> -- that was just read? its not documented. . .
It is now ;-).
> write h to file newFile
> --OK, so h is obviously the date just read from the socket
> read from socket g with message "moreData"
> -- same question as above. . .why not just stick with
> -- socket transPasvIP?
> end moreData
>
> Thanks! building little widgets that get specific files and posts them back
> automatically makes life sooo easy. (thanks andu!) if anyone is interested
> in seeing the scripts for this FTP work in progress, email me off list.
>
> Hinduism Today
>
> Sivakatirswami
Andu
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
