zsh-workers
 help / color / mirror / code / Atom feed
From: DervishD <raul@pleyades.net>
To: Zsh Workers <zsh-workers@sunsite.dk>
Subject: About the zftp module
Date: Sun, 11 Jan 2004 16:07:01 +0100	[thread overview]
Message-ID: <20040111150701.GA29092@DervishD> (raw)

    Hi all :))

    This message is directed mainly to Peter Stephenson, who is AFAIK
the author of the zftp module, but anyone interested is welcome ;)

    In zsh 4.0.9, the main problems of zsh/zftp still are there: lack
of signal handling, which makes impossible to stop a transfer, large
transfers (any transfer so long that makes the control connection
dissapear) make zftp hang (it doesn't respond when the transfer is
finished), etc... I want to make clear that some of this behaviour
can be, as always, my fault.

    My question is: are plans to solve this in future versions? In
this state, zsh/zftp is almost unusable, but OTOH is the better ftp
client I've ever used, since I can use the full power of zsh command
line handling with it. I really like it, but for me is very annoying
to have to stop transfer using 'kill -9', and things like that.

    I have a unfinished proyect (although usable, I think) of TCP and
UDP sockets, that support timeouts and nonblocking transfers, that
can be useful for zftp. It is unfinished and undocumented, but since
is a wrapper around the socket interface, it's pretty easy to use.
It's just that: an object oriented wrapper encapsulating the socket
access in an easy and simple interface, written in C and GPL'd. If
you want to take a look at it, feel free to ask. This may or may not
be a partial solution: I have read some of the code of the zftp module
and I'm not sure that my code will be suitable, but there is nothing
to loose in suggesting ;))

    As an interim solution what I do is to run zftp in a separate
interactive shell instance, so if I must kill it I don't loose my
background jobs and the like.

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/


                 reply	other threads:[~2004-01-11 15:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040111150701.GA29092@DervishD \
    --to=raul@pleyades.net \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).