unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Barry Margolin <barmar@alum.mit.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: About "capabilities of server"
Date: Sun, 07 Apr 2013 13:29:28 -0400	[thread overview]
Message-ID: <barmar-FDB0E5.13292807042013@news.eternal-september.org> (raw)
In-Reply-To: mailman.23712.1365342356.855.help-gnu-emacs@gnu.org

In article <mailman.23712.1365342356.855.help-gnu-emacs@gnu.org>,
 Michael Albinus <michael.albinus@gmx.de> wrote:

> Christopher Schmidt <christopher@ch.ristopher.com> writes:
> 
> > Xue Fuqiao <xfq.free@gmail.com> writes:
> >> In the doc string of `open-network-stream' and
> >> `notifications-get-capabilities', "capabilities of server" are
> >> mentioned.  What does it mean?  I have done RTFM and STFW, but I didn't
> >> get some useful information.  Sorry if it's off-topic for Emacs.
> >
> > Take a look RFC 1869, for example.
> >
> >     https://tools.ietf.org/html/rfc1869
> 
> This one is for SMTP servers. I doubt, it is related to
> `open-network-stream' and `notifications-get-capabilities'.

It's related to open-network-stream. The capabilities-related options 
are generic, intended to work with a variety of protocols.

The general idea is that many application protocols have optional 
features, and a way for the client to ask the server "Which features do 
you support?". This is what the Elisp documentation refers to as its 
capabilities.  You specify the command used to get the list of 
capabilities in the :cabability-command option.

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***


  parent reply	other threads:[~2013-04-07 17:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-07 12:43 About "capabilities of server" Xue Fuqiao
2013-04-07 13:02 ` Christopher Schmidt
2013-04-07 13:45   ` Michael Albinus
2013-04-07 14:04     ` Christopher Schmidt
     [not found]   ` <mailman.23712.1365342356.855.help-gnu-emacs@gnu.org>
2013-04-07 17:29     ` Barry Margolin [this message]
2013-04-07 22:47       ` Xue Fuqiao

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=barmar-FDB0E5.13292807042013@news.eternal-september.org \
    --to=barmar@alum.mit.edu \
    --cc=help-gnu-emacs@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.
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).