Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate Neovim process handler to remove Node.js dependency #9

Open
rhysd opened this issue Dec 22, 2015 · 0 comments
Open

Separate Neovim process handler to remove Node.js dependency #9

rhysd opened this issue Dec 22, 2015 · 0 comments
Assignees

Comments

@rhysd
Copy link
Owner

rhysd commented Dec 22, 2015

Currently <neovim-editor> component requires child_process module to invoke Neovim process and communicate with msgpack-rpc API using stdio. However, the way to communicate with Neovim is not only stdio.
It is also available to use network for communication with Neovim process. Web applications can communicate with remote Neovim process via WebSocket. If we connect to Neovim process via WebSocket, Neovim Chrome extension is feasible. Chrome extension can't invoke process because of sandbox but can communicate with external process via websocket. Web services can also do.

So I want to separate the module depending on child_process. Current process handler will be changed to use client interface (Nvim in 'promised-neovim-client'?) and users will be able to specify their original client (which may use WebSocket, HTTP, and so on).

This change doesn't affect public API because users get client instance via editor.getClient() API.

@rhysd rhysd self-assigned this Feb 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant