From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: A femtolisp based emacs clone
Date: Fri, 26 Aug 2016 10:28:29 +0200 [thread overview]
Message-ID: <871t1cgcia.fsf@gmx.de> (raw)
In-Reply-To: <jwva8g1qc2k.fsf-monnier+gmane.emacs.help@gnu.org> (Stefan Monnier's message of "Thu, 25 Aug 2016 08:28:32 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Indeed. I think you could get the best of both worlds by using an
> approach similar to Tramp but running a little tramp-daemon on the other
> end, such that we can use a more efficient communication protocol
> (e.g. when saving a file we could locally diff it against the last
> version (of which the remote daemon would also keep a copy), and then
> only send the diff).
>
> This said, even using such a daemon it might be difficult to get good
> performance: part of the problem is the number of round-trips.
> E.g. when saving a file we have to check if the file was modified in the
> mean time and whether saving into a new inode would change the owner
> (etc...), which each require a round-trip. To get rid of these
> round-trips, we'd have to shortcut this code and delegate the
> higher-level "save file" operation to the remote server, which then has
> to perform those tasks but still obeying the locally set customizations
> about how to do each one of those tasks.
A while ago, Tramp has tried this approach, using the FISH protocol
(<https://en.wikipedia.org/wiki/Files_transferred_over_shell_protocol>).
Experience was bad wrt performance, so Tramp removed this protocol meanwhile.
But I'm open to restart such an implementation, if there would be a
better protocol. Preferred an existing one, but we could also design an
own (and write then the server part as well).
> Stefan
Best regards, Michael.
next prev parent reply other threads:[~2016-08-26 8:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-21 20:15 A femtolisp based emacs clone edu500ac
2016-08-22 4:17 ` Gene
2016-08-22 5:22 ` Rusi
2016-08-22 21:32 ` edu500ac
2016-08-23 1:23 ` Thien-Thi Nguyen
2016-08-24 3:52 ` James K. Lowden
2016-08-24 4:35 ` Yuri Khan
2016-08-24 21:38 ` edu500ac
2016-08-25 12:28 ` Stefan Monnier
2016-08-26 8:28 ` Michael Albinus [this message]
2016-08-26 13:08 ` Stefan Monnier
2016-08-25 21:22 ` Ben Bacarisse
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871t1cgcia.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).