all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Richard <youngfrog@members.fsf.org>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: A (probably silly) problem with request.el
Date: Mon, 08 Jun 2015 07:36:39 +0200	[thread overview]
Message-ID: <87zj4arcbc.fsf@members.fsf.org> (raw)
In-Reply-To: <87mw0c7ejj.fsf@mbork.pl> (Marcin Borkowski's message of "Sat, 06 Jun 2015 22:44:16 +0200")

Marcin Borkowski <mbork@mbork.pl> writes:
> OK, so now that I played with it for a moment, let me ask more questions
> (not very urgent ones, I'm just curious).  Do I get it correctly that
> the "success" function will be called *at some later point* (assuming
> that the request succeeded)?

Yes.

>                               What Emacs mechanism is used for that -
> timers?

I don't think so.

>          (I assume that the asynchronicity is more or less natural when
> using curl, and then async processes are used, right?  

I don't know the internals of request.el (I never used it, and
discovered it when reading this thread), but that would be my guess too.

>                                                        Does url.el also
> use some external tool?)

Network processes are also asynchronous in emacs. See
make-network-process for the low lever thing, and url-retrieve.

Best,

-- 
Nico.



  reply	other threads:[~2015-06-08  5:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 21:12 A (probably silly) problem with request.el Marcin Borkowski
2015-06-05 10:09 ` Nicolas Richard
2015-06-05 14:02   ` Marcin Borkowski
2015-06-05 15:40     ` Nicolas Richard
2015-06-05 21:26       ` Marcin Borkowski
2015-06-06 19:25         ` Nicolas Richard
2015-06-06 20:31           ` Marcin Borkowski
2015-06-06 20:44           ` Marcin Borkowski
2015-06-08  5:36             ` Nicolas Richard [this message]
2015-06-10 21:58           ` Marcin Borkowski
2015-06-10 22:15             ` John Mastro

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=87zj4arcbc.fsf@members.fsf.org \
    --to=youngfrog@members.fsf.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=mbork@mbork.pl \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.