Hi Stephan,

Thanks for the reply. These commands ("neighbor list", "neighbor protocols" and "neighbor connections") are indeed in the ExtendedApiHandler.cpp file (line 344 [2]), though the daemon [1] answers with 400 UNKNOWN COMMAND for the last two commands.

I wonder why these are not presented in the documentation and the reason why one should switch into protocol extended is quite opaque in the documentation. I'll work on a PR if I can get free time this week.

[1]: IBR-DTN 1.0.1 (build 1d1df7b) API 1.0


Best regards,
---
​​
Auzias
Maël
auzias.net - vcard - thesis
GSM: 0033 695 118 774

On Sat, Jan 14, 2017 at 11:57 AM, Stephan Rottmann <rottmann@ibr.cs.tu-bs.de> wrote:
Hi Maël,

in https://github.com/ibrdtn/ibrdtn/tree/master/ibrdtn/daemon/doc
there is a file api.tex which has a list of the commands.

Some commands are still missing (in the extended section, you can use
"neighbor protocols" and "neighbor connections", to see which links are
available to the neighboring nodes.

Best regards,
Stephan



Am Donnerstag, den 12.01.2017, 09:51 +0100 schrieb Maël Auzias:
> Hi y'all and happy new year.
>
> According to the documentation it is possible to "switch to the
> ExtendedAPI" to register an endpoint, send/receive bundles and so on.
>
> According to the source code there is no mention of any APIHandler
> (non Extended) yet there is a APIServer class and
> a ApiP2PExtensionHandler class. However these class are nothing like
> ExtendedApiHandler.cpp file.
>
> I wonder why the command "protocol extended" is needed and what are
> the possible commands out of the extended protocol.
>
> Have a nice day!
>
> Best regards,
> ---
> Auzias Maël
> auzias.net - vcard - thesis
> GSM: 0033 695 118 774
> -- 
> !! This message is brought to you via the `ibr-dtn' mailing list.
> !! Please do not reply to this message to unsubscribe. To unsubscribe
> or adjust
> !! your settings, send a mail message to <ibr-dtn-request@ibr.cs.tu-b
> s.de>
> !! or look at https://mail.ibr.cs.tu-bs.de/listinfo/ibr-dtn.