[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Help writing transport
From: |
Christian Grothoff |
Subject: |
Re: Help writing transport |
Date: |
Fri, 28 Feb 2020 22:27:48 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 |
Hi Dan,
We're currently re-writing transport, which likely makes the current
code WAY more messy to understand as both old and new live side-by-side
in the repo.
Anyway, to answer your question, the best place to look is
src/include/gnunet_transport_communication_service.h. If you use *this*
API to talk to transport (instead of a fifo), your HAM code should just
be able to 'register' itself with the (next generation) transport
service as a communicator and transport will then use it when it can.
If you cannot understand the API from reading the (commented) header,
there are existing examples of communicators in transport/.
I hope this helps!
Happy hacking!
Christian
On 2/28/20 8:38 PM, danielp3344--- via Mailinglist for GNUnet developers
wrote:
> Hi all,
>
> I'm trying to get GNUnet to work over ham radio. I wrote all my radio
> related code separately for now, all GNUnet needs to do is write any
> data it wants transmitted into a fifo, and read back any data that comes
> through. All the error correction, validation etc is done by the radio
> code, all GNUnet will see is the valid packets that are received.
> However the docs are not incredibly helpful and after reading some of
> the existing files in src/transport/ I'm still not really sure where to
> start. Any help would be appreciated.
>
> Thanks,
> -Dan
signature.asc
Description: OpenPGP digital signature