Re: [Armory-devel] Server/agent

[Robert K. <ny...@gm...>]

First of all, thank you very much Ananth for your response.


> 1) Dynamically linked plugins. I think it's a must both for server and
> > agents. It will enable us to better divide responsibilities, avoid
> clashes
> > in SVN and add new features without recompiling the whole app.
>
> The statistics gathering programs will be compiled into shared libs.
> The agent will be linked with these shared libs.


That's good. Though, if I understand correctly, it can be done better.
Instead of linking executables with statistics gathering modules during the
build process, we can use dlopen/dlsym (or LoadLibrary/GetProcAddress in
Windows) to link in run-time.

> 4) Networking library. Depends on all of the above.
>
> Darrik (another developer) and myself were discussing about which
> framework to use (Qt, ACE or Boost), but unfortunately he had to leave
> the project. I'm somewhat familiar with ACE and I think it is ideal
> for our requirements.


I admit I have only theoretical knowledge of ACE. It really seems to be the
right choice for the server. It also seems too heavyweight for agents.
Depending on the communication protocol we agree on, it might be better to
use two networking libraries, one for the server and another one for agents.

So far I was able to get in touch with only 3 out of 11 registered
developers (excluding Darrik who left and myself). The project seems to be
stalled. There is almost no activity, no proof that we are making any
progress. It kills peoples' motivation to participate in the project.
On SourceForge.net there's a nice tracker and a tasks system. We could
create some basic tasks and then gradually work out a design of the project
. Then divide responsibilities, assign tasks and write proper code.
Does anyone have a better idea?