alternative methods besides TCP

[prabirshrestha]

The problem with TCP is that the port is exposed and a malicious app can listen and write to it.
Are there plans to provide alternative protocol such as named pipes.

[roxma]

Fair point.

This plugin currently supports neovim_rpc#jobstart, using stdin, stdout for the channel.

Looks like unix domain socket is a better option, as the v:servername on neovim. It seems named pipe needs to be created each time for each rpc connection

[lilydjwg]

Recently I have installed this to use deoplete. Just now I sudo vim some file, and suddenly realize that, if any of those highly-restricted services (mostly dedicated user, no root, no normal file system access) running on my machine actually do something terrible, my system will be pwned easily....

[lilydjwg]

It's sad that Vim doesn't support UNIX domain sockets :-(

[roxma]

The commit 5a20db1 enables unix socke based rpc server.

It seems it doesn't boost the time performance except for the security improvement.

Unfortunately there's still an internal vim server which is using tcp. It's hard to change this because :help ch_open only supports TCP.