[Nfd-dev] UNIX stream faces

[Davide Pesavento]

Understood. In that case, yes, you need to write a custom transport,
say FooTransport, as a subclass of Transport. If you need to
communicate with another daemon via a Unix socket for packet
transmission, FooTransport should take care of connecting to that
daemon's socket. Then you need to implement a FooFactory, subclass of
ProtocolFactory. Optionally, only if you need unicast faces, you will
also need a FooChannel.

Davide

On Tue, Jan 23, 2018 at 3:39 PM, Anthony Dowling <dowlinah at clarkson.edu> wrote:
> I'm trying to build a customized transmission system, and at first I had
> thought of using UNIX sockets to communicate with it. However, I saw that
> NFD also supports building custom transports; would that be enough to
> interface to a non-standard device (i.e. a different broadcast medium than
> wifi)?
>
> Thanks,
> Anthony
>
>
> On Tue, Jan 23, 2018 at 3:29 PM, Davide Pesavento <davide.pesavento at lip6.fr>
> wrote:
>>
>> Hi Anthony,
>>
>> Outbound Unix sockets don't make sense. It would mean that one NFD
>> instance "connects" to another NFD on the same machine.
>> Can you tell us a bit more about what you're trying to do? What's your
>> use case and why do you need Unix sockets?
>>
>> Thanks,
>> Davide
>>
>> On Tue, Jan 23, 2018 at 3:01 PM, Anthony Dowling <dowlinah at clarkson.edu>
>> wrote:
>> > Hello all,
>> >
>> > I was trying to connect NFD to a UNIX socket face, and found that UNIX
>> > sockets are inbound only according to the developers guide. Is there a
>> > way
>> > to make it so that there is an outbound UNIX socket from NFD? If not,
>> > where
>> > should I start looking to make one? Also, is there a reason that UNIX
>> > sockets are inbound only?
>> >
>> > Thanks,
>> > Anthony Dowling
>> >
>> > _______________________________________________
>> > Nfd-dev mailing list
>> > Nfd-dev at lists.cs.ucla.edu
>> > http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>> >
>
>