[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: non-blocking connect
From: |
Kai Grossjohann |
Subject: |
Re: non-blocking connect |
Date: |
Thu, 04 Nov 2004 16:21:57 +0100 |
User-agent: |
Gnus/5.110003 (No Gnus v0.3) Emacs/21.3.50 (gnu/linux) |
Jochem Kossen <address@hidden> writes:
> So, the things i suspect might have something to do with it:
> - chunksize (what does the default do in comparison with values like
> 500/1024/2048)? I read the documentation, but it doesn't mention
> what tramp does if it's set to nil.
Setting tramp-chunksize to 500 means that Tramp will send 500 bytes of
data, then wait a bit before sending the next chunk of data.
Setting tramp-chunksize to nil means that Tramp will send all of the
data at once, unchunked, so to speak. (For instance, for writing a
file via base64 inline encoding, Tramp would base64-encode the buffer
contents, then send the whole encoded buffer to the remote end at once
with a single process-send-region invocation.)
Kai
- Re: non-blocking connect, Richard Stallman, 2004/11/04
- Re: non-blocking connect, Jochem Kossen, 2004/11/04
- Re: non-blocking connect,
Kai Grossjohann <=
- Re: non-blocking connect, Richard Stallman, 2004/11/05
- Re: non-blocking connect, Stefan, 2004/11/08
- Re: non-blocking connect, Kai Grossjohann, 2004/11/08
- Re: non-blocking connect, Stefan Monnier, 2004/11/08
- Re: non-blocking connect, Kai Grossjohann, 2004/11/09
- Re: non-blocking connect, Stefan, 2004/11/09
- Re: non-blocking connect, Kai Grossjohann, 2004/11/10