Hello Stephen, On Wed, Oct 09, 2013 at 05:34:00PM +0100, Stephen Thornton wrote: > I am currently developing a mesh router solution for several clients. I have > been using batman-adv in this project for almost a year (using OpenWRT), and > it has all worked fantastically. Thanks so much guys.
thank you :)
> I now have a requirement for GPS logging functionality, along with passing
> other data between nodes. I have already written a simple layer3 protocol for
> this purpose, but this was before ALFRED. ALFRED provides almost all the
> functionality I need apart from the fact that I really need to embed the
> alfred code within my own application. I could use it as is via a sys call,
> but it would be so much better to include the code. What are your feelings
> regarding splitting the alfred code into a library with can be included in
> other user applications, and an alfred client program that uses this library?
> I'm quite prepared to give quite a bit of my own time to doing this if you
> like the idea.
Well, the alfred binary does quite a few things and relies on being a process
on it's own. I don't think
it's easy to integrate that functionality in a library, and it is not intended.
What we'd like to encourage however is to interface directly with alfred by
talking to it through
the unix socket - have a look at vis (already implemented) or the gpsd support
andrew recently
proposed. You could do the same for your application - talk to alfred directly.
That should also
be the best solution in regard of long term maintainance, license issues
(alfred is GPL after all), ...
If you feel that alfred really needs to be binary-integrated in your
application, I'd like to know why. :)
Cheers,
Simon
signature.asc
Description: Digital signature
