Send a PM via linuxdcpp.pipe

[lagalopex]

As mentioned in Bug 361735 its much more usefull when the communication would be bidirectional.
But for now I can send a PM to known user on a known host.

"say the_hub_url|the_nick|my_message" > linuxdcpp.pipe

It's enough for a small announcments, where the nicks are known. (offline user will be silently ignored.)

[Razzloss (razzloss)]

Yeah, my patch shouldn't be taken as an example. It was bad. To do this properly all *Manager calls should be moved to a _client function which is called from the GUI thread via WulforManager::distpacthClientFunc.

Even if this is fixed, I don't think it will be included in the main trunk (Steven comments?). I'd rather have some bi-directional communication for features like this, as mentioned in the bug #361735.

--RZ

[Steven Sheehy (steven-sheehy)]

I don't think this is suitable for the main trunk, perhaps as a plugin in the future. This sounds like you want to turn linuxdcpp into a daemon with a detached, possibly remote user interface to allow for rich, bi-directional communication between the two. This is outside the scope of our pipe, which is to be used to send simple commands to an existing instance because either the user didn't know of/couldn't find the existing process or to respond to some event that linuxdcpp is registered for (i.e. magnet URI).

[lagalopex (lagalopex)]

I run linuxdcpp on a server and access it via vnc. With this patch I am able to run a script to notify some users.
If it's done by patch or plugin I don't even know linuxdcpp has a plugin-interface?!
Just wanted to share the patch. When the IPC is implemeted via dbus it will be possible, right?

[Razzloss (razzloss)]

Yeah, we don't have a plugin interface. It's been on a todo list for a loooong time, but maybe if the dcpp-core gets a plugin interface in the future, we'll be able to use that.

--RZ