From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Connection drops data if it sent too quickly
Date: 06 Feb 2003 00:31:18 +0100 [thread overview]
Message-ID: <5xlm0u71a1.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <nqu1filpin.fsf@alcatel.de>
Michael Albinus <Michael.Albinus@alcatel.de> writes:
> Richard Stallman <rms@gnu.org> writes:
>
> > Perhaps we should put that into process-send-string so that Lisp code
> > won't need to concern itself with this issue. But I wonder
> > whether the bug is in ssh. If so, that's the place to fix it.
> >
> > If Emacs is talking to some other program instead, does the same
> > bug happen?
>
> I've written some few lines which reproduce the problem under HP-UX
> with all Emacsen available for me (20.7, 21.2, 21.2.93):
>
> (with-temp-buffer
> (let ((bytes 1000)
> (proc (start-process (buffer-name) (current-buffer) "wc" "-c")))
> (process-send-string proc (make-string bytes ?x))
> (process-send-eof proc)
> (process-send-eof proc)
> (accept-process-output proc 1)
> (goto-char (point-min))
> (re-search-forward "\\w+")
> (message "Bytes sent: %s\tBytes received: %s" bytes (match-string 0))))
>
> No problem under other Unices, like Solaris.
So this sounds like a HP-UX specific problem.
As such, it would be great if the current 0.1 second chunk delay (and
similar delay in tramp-send-linewise) was a defvar which could be set
to 0.0 on non-HPUX (and non-Tru64) platforms.
That would make tramp run MUCH faster. I tried this on GNU/Linux, and
it makes a huge difference!
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2003-02-05 23:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 20:37 Connection drops data if it sent too quickly Kai Großjohann
2003-02-04 10:49 ` Michael Albinus
2003-02-04 15:42 ` Richard Stallman
2003-02-05 15:24 ` Michael Albinus
2003-02-05 23:31 ` Kim F. Storm [this message]
2003-02-06 7:45 ` Michael Albinus
2003-02-07 18:31 ` Kai Großjohann
2003-02-07 23:10 ` Richard Stallman
2003-02-06 15:40 ` Richard Stallman
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=5xlm0u71a1.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.