add commandline server about tern HOT 4 CLOSED

The HTTP server isn't for in-browser editors, it is specifically for desktop editors. HTTP is a nice, flexible, widely supported communication method, so I see no reason not to use it here.

from tern.

Quick, but not helpful. I'm speaking from over 10 years of experience writing Vim plugins, for different languages, have actually written an Emacs plugin once, and was thinking of offering to help with the Vim side here. Keeping an open mind would help encourage collaboration.

HTTP is neither the only, nor the first, nor the best interprocess communication protocol. There is a reason why Emacs supports asynchronous subprocesses, and why Vim plugin authors borrow such support.

from tern.

I'm not saying async subprocesses don't work. I'm saying HTTP works for me, and I see no reason to move away from it. It would be very easy to have a version of desktop.js that does stdin/stdout communication instead of HTTP (if someone wants to write one, I'll be happy to factor out things like .tern-project parsing once it gets more complex, so that they can be shared).

But no, I'm not going to drop my approach just because you are used to another approach.

from tern.

I tried to suggest plain socket communication instead of http server as well (#7) because from my limited amount of vim plugin writing i'd find that more appropriate. But @marijnh disagrees obviously.

from tern.