klaus schilling <schilling.kl...@web.de> wrote: > Hello, > I just noticed the recent addition of a remote control feature by means > of a fifo. As it only uses one fifo, the interaction is unidirectional, > and the output of a command gets lost in the land of nowhere. > > Will it be possible later on to add support for bidirectional remote > control, either by means of a second fifo or by sockets (tcp/ip or unix > namespace) that can be accessed via socat, similar to uzbl's core > functionality? This would allow to control vimb semi-interactively via > shell scripts and expect.
I changed my mind. Bidirectional communication is useful in conjunction with :eval command. This would allow to run JavaScript in the current webview to retrieve some nice data, like all links on the page. I think this would allow to write nice scripts for vimb. I started to implement the socket stuff and I need some feedback where to go with the remote control. At the time vimb supports only a control fifo. This was added because it seemed to be enough and it's much simplier to use than a socket. But a socket can be use nearly as easy like a fifo. For me it would be a overkill to provide both remote channels fifo and socket and I tent to remove the fifo support soon (it's not part of a release - so I hope this will not hurt too much). Are there reasons to keep the fifo also when there is socket support? Daniel ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ vimb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vimb-users
