Skip to content
This repository has been archived by the owner on Jul 23, 2024. It is now read-only.

use stdio for communication? #17

Open
lilydjwg opened this issue Dec 23, 2017 · 2 comments
Open

use stdio for communication? #17

lilydjwg opened this issue Dec 23, 2017 · 2 comments

Comments

@lilydjwg
Copy link

Hi, I'm considering using stdio to communicate with the Python process, to avoid security issues I've talked about in #1. What do you think about this idea?

PS: Firefox uses stdio for extensions to communicate with its native application too.

@roxma
Copy link
Owner

roxma commented Dec 23, 2017

  • stdio has bad performance on Windows
  • It would be impossible for a plugin to create threads which hold its own RPC connection. NCM uses multithreading.

I think it's better to use unix socket on linux system.

@roxma
Copy link
Owner

roxma commented Dec 23, 2017

By the way, there're two servers in this plugin. Read https://github.com/roxma/vim-hug-neovim-rpc#overall-implementation

The VIM server, which talks to vim8 using vim8's RPC. It's running in the same process as vim, so it's impossible to use stdio without changing current implementation

The NVIM server, which talks to the RPC clients. Both servers is using tcp for communication.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants