Am 14.01.2014 13:22, schrieb Shyam B:
I looked up the internet, but I could not get a clear idea on how to use the QueueBundleEvent. Is that a plugin or do I have to register the event in the code directly?
That is an internal event of the daemon, which is exposed in the standard logging and available through the event API.
Where is the standard API connection? And what is an extended protocol? Until now, I understand using the tools and have myself made changes to the Ibrdtn C++ tools and I understand workings of ibrdtnd.conf and reading the neighbors via localhost query. However, was curious where/how you got the 'stream' information? Is it the same way we query for the DTN neighbors (say, opening a socket using a python script)?
Extended protocol is the standard API for applications. You use it by connecting with TCP to the daemon on port 4550 and then send the command "protocol extended" to change into that mode. The same way you can switch to other API protocols like "protocol management" and "protocol event". By using the management API you can query the neighbors.
Kind regards, Johannes Morgenroth