Aleksandar Fabijanic

https://macchina.io/docs/00150-RemotingNGTutorialPart1.html https://macchina.io/docs/00151-RemotingNGTutorialPart2.html

Thnks @uilianries, by all means - please feel free to work on it and send pull request, we'll be happy to review and merge it. also, you may want to...

cool, #53 would also be nice to have, if you are inclined to put in some effort there.

1. only dynamic is fine - since it is a dynamic plugin framework, static linking does not really make sense 2. > Does libv8.so should be copied to target lib...

@obiltschnig this is duplicate of #41; I'm thinking it should be done in poco, not here?

@Bjoe see with @uilianries, he may be working on it

> Isn't it useful to either define Poco as a dependency or to integrate Poco completely as a Git submodule? it is, but there are sticky points, like OSP and...

git submodule is proper solution; however, it requires buildsystem changes because poco libraries are now spread directly under platform directory. OSP should also be moved into separate repository and included...

Hi David, thanks for answering. Please see my replies below. > 1/ ... Have you seen duplicates when debugging ? Yes, since [the IDs sent](https://github.com/DavidKeller/kademlia/blob/master/src/kademlia/engine.hpp#L442) are not the real peer...

> The purpose of `refresh_id[ i ] = ! refresh_id[ i ];` id to generate at each iteration Key IDs further away from our Node IDs to contact nodes that...