From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Peter Stephenson" <pws@cambridgesiliconradio.com>,
"Zsh hackers list" <zsh-workers@sunsite.auc.dk>
Subject: RE: Proxy support for zftp functions
Date: Mon, 22 May 2000 20:35:53 +0400 [thread overview]
Message-ID: <001101bfc40b$cc325c00$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <0FUY009QZYKZGE@la-la.cambridgesiliconradio.com>
> >
> > Yes, it makes more sense. Proxy is relevant only for a
> logon - then it
> > is completely transparent (hopefully :-).
>
> Actually, for just that reason, your idea of doing it in the
> functions is
> probably better. The less hidden code the more I like it.
>
May be. For a start function is easier, of course.
> > Actually, much more interesting (needed) feature is ls parsing.
> > Currently, zftp relies on MDTM/SIZE to exist - and,
> unfortunately, they
> > are missing in "common" Unix servers. Have you ever thought
> about it?
>
> There's a nice project for someone with a bit of time. This
> can probably
> be done in shell functions too --- it's system-specific, so
> not good to
> hard code, and the only place this is used internally is for
> supplying to
> functions doing progress reports, which can be rewritten to
> use information
> returned by ls where necessary.
>
The main use for it is to be able to compare times on remote/local
files. Without it no real directory sync (and even reliable reget) is
possible. Is it possible to pass file date/size from function to zftp.c
code? O.K., file mtime can be set by function as well ...
There are some possibilities:
- use external Perl code. The excellent piece of work is Mirror, that
understands a dozen remote systems (inluding DOS-based FTP server! Wow!
:-) That may do for a start, but thinking about calling Perl every time
I need to parse ls line makes me shudder. What is the status of Perl
module for Zsh? It would make life much easier.
- rewrite Perl modules (system detection + parsing routines) in Zsh.
They are based on regexps, so it is doable (but needs some time, of
course).
If we had working Perl module, I would favour the first approach. No
need to reinvent the wheel.
-andrej
next prev parent reply other threads:[~2000-05-22 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-22 15:01 Andrej Borsenkow
2000-05-22 15:33 ` Peter Stephenson
2000-05-22 16:03 ` Andrej Borsenkow
2000-05-22 16:17 ` Peter Stephenson
2000-05-22 16:35 ` Andrej Borsenkow [this message]
2000-05-22 17:04 ` Peter Stephenson
2000-05-23 0:19 ` Bart Schaefer
2000-05-23 0:43 ` Bart Schaefer
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='001101bfc40b$cc325c00$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=pws@cambridgesiliconradio.com \
--cc=zsh-workers@sunsite.auc.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).