unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Zhu Zihao" <all_but_last@163.com>
To: "Stefan Monnier" <monnier@iro.umontreal.ca>
Cc: Philipp Stephani <p.stephani2@gmail.com>,
	Akira Kyle <ak@akirakyle.com>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re:Re: "Asynchronous Requests from Emacs Dynamic Modules"
Date: Fri, 20 Nov 2020 23:54:48 +0800 (CST)	[thread overview]
Message-ID: <47fe3996.8d32.175e65d7ede.Coremail.all_but_last@163.com> (raw)
In-Reply-To: <jwv361u8svy.fsf-monnier+emacs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]

Ok, But how to do this in Emacs version 25-27?


Emacs doesn't support named pipe access, but may be we can use `make-network-process` to open a TCP socket. Like this?


```
(let ((proc (make-network-process :name "fake-proxy-process"
                     :server t
                     :host 'local
                     :filter <filter-to-execute-callback>
                     :noquery t
                     ;; Detect port automatically
                     :service t)))
     (setq <global-proc-var> proc)
     (module-function-initialize-notify (process-contact proc :service)))
```


But this maybe too strange for user to understand why a dynamic module require a TCP port access...






At 2020-10-31 20:49:21, "Stefan Monnier" <monnier@iro.umontreal.ca> wrote:
>> With Emacs 28, you can get a file descriptor to a pipe process and
>> send arbitrary data there (from arbitrary threads).
>
>Cool, so that takes care of it.
>
>> You'd still need some small protocol (e.g. JSON) to encode/decode
>> requests, but with that you can send arbitrary requests
>> back asynchronously.
>
>I don't think you need a complex protocol: just stash somewhere (inside
>the module data structures) the data you need for the async request,
>then send a dummy byte to the pipe.  On the Lisp side, just install
>a process-filter which calls back the module to "run any pending async
>requests".
>
>
>        Stefan
>

[-- Attachment #2: Type: text/html, Size: 2385 bytes --]

  parent reply	other threads:[~2020-11-20 15:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-30 21:35 "Asynchronous Requests from Emacs Dynamic Modules" Akira Kyle
2020-10-30 22:39 ` Stefan Monnier
2020-10-31  3:18 ` Zhu Zihao
2020-10-31  7:45   ` Eli Zaretskii
2020-10-31  8:02     ` yyoncho
2020-10-31  9:13       ` Eli Zaretskii
2020-10-31  9:45         ` yyoncho
2020-10-31 10:43           ` Eli Zaretskii
2020-10-31 19:25             ` Akira Kyle
2020-10-31 20:18               ` Eli Zaretskii
2020-11-01  0:14                 ` Akira Kyle
2020-11-01 18:28                   ` Eli Zaretskii
2020-11-01 20:15                     ` Akira Kyle
2020-11-01 20:51                       ` async-await (was: Re: "Asynchronous Requests from Emacs Dynamic Modules") Philipp Stephani
2020-11-02 15:22                       ` "Asynchronous Requests from Emacs Dynamic Modules" Eli Zaretskii
2020-10-31  7:36 ` Philipp Stephani
2020-10-31 12:49   ` Stefan Monnier
2020-11-01 20:18     ` Akira Kyle
2020-11-01 20:32       ` Philipp Stephani
2020-11-20 15:54     ` Zhu Zihao [this message]
2020-11-20 16:04       ` Robert Pluim

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=47fe3996.8d32.175e65d7ede.Coremail.all_but_last@163.com \
    --to=all_but_last@163.com \
    --cc=ak@akirakyle.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=p.stephani2@gmail.com \
    /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 public inbox

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

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).