Re: Implementing image support for kitty terminal

[Eli Zaretskii <eliz@gnu.org>]

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Gerd Möllmann <gerd.moellmann@gmail.com>,
>   emacs-devel@gnu.org,
>   jao@gnu.org
> Date: Fri, 09 Sep 2022 08:19:44 -0400
> 
> >> Or even, do we still have terminals connected with, don't know, say 1200 
> >> baud or some such?
> > I don't think so, but we do have slow net links and ssh logins.
> 
> I wonder how this interacts with our display optimizations, to be
> honest: slow network connections tend to suffer mostly in terms of
> "packets per second" rather than "bytes per second", so an optimization
> makes a difference only if it changes the size of a display update
> from N+1 packets to N packets (or fewer).
> 
> E.g. when our display updates (counted in bytes and without frame-based
> redisplay) fall below the "1 packet" limit (which I presume is around
> 1.5kB), then using frame-based redisplay doesn't make any noticeable
> difference to "ssh logins over congested/slow networks".

The theory is well-understood, I think.  What we need is measurements
in various usage scenarios.

Btw, slow/congested network suffer not only from packet per second
issue, but also from packet loss.