Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: gsf@fruct.us (Gabriel Sean Farrell)
Subject: [sup-talk] Persistence between IMAP clients
Date: Thu, 7 Feb 2008 15:12:34 -0500	[thread overview]
Message-ID: <20080207201234.GB18001@manheim.library.drexel.edu> (raw)
In-Reply-To: <1202407800-sup-6982@south>

On Thu, Feb 07, 2008 at 10:12:43AM -0800, William Morgan wrote:
> Why is it that people are so excited about having an email clients with
> this crazy client/server architecture? We don't demand that of any other
> console program we use.

Let's see, what console programs do I have open right now?  Mutt, irssi,
lynx, tintin++, and btlaunchmanycurses.  We've already discussed Mutt.
irssi is a great example of a console program that acts as a client to a
server.  lynx is an example of the most commonly understood
client/server relationship today.  tintin++ is a mud client, and the
improvements it has over simple telnet clients in the specific domain of
muds could serve as a model for others that rely on ssh/sftp/etc for
other domains.  btlaunchmanycurses is a curses bittorrent client and,
being bittorrent, connects to other clients instead of a server.
Nonetheless, it demonstrates another protocol that I choose a console UI
for.

Even Vim provides the option of editing via sftp and scp, essentially
creating a client connection to files on a server.  It's a pretty
fantastic feature that I recommend you try out if you haven't done so
already.

> If you can run a sup server somewhere, surely you can run sshd there
> instead. The only difference would be UI lag on slow connections. Is
> that the big win?

The ability to access these programs over ssh is part of the reason I
use them, but I prefer running them on the local box because UI lag and
dropped connections have frustrated me enough that I'd rather not deal
with them when I don't have to.


  reply	other threads:[~2008-02-07 20:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04 15:12 Gabriel Sean Farrell
2008-02-04 18:46 ` John Bent
2008-02-05 21:03   ` Gabriel Sean Farrell
2008-02-05 16:42 ` William Morgan
2008-02-05 19:12   ` Magnus Therning
2008-02-05 19:51     ` William Morgan
2008-02-05 21:11   ` Gabriel Sean Farrell
2008-02-05 22:02   ` William Morgan
2008-02-06 22:37     ` Gabriel Sean Farrell
2008-02-07  8:45     ` Marcus Williams
2008-02-07 18:12       ` William Morgan
2008-02-07 20:12         ` Gabriel Sean Farrell [this message]
2008-02-07 21:09         ` Marcus Williams

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=20080207201234.GB18001@manheim.library.drexel.edu \
    --to=gsf@fruct.us \
    /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