Lines Matching full:hook

125 needs, and may assign whatever meaning it wants to a hook.
130 A hook has an
145 A hook is always connected to another hook.
148 removing either hook destroys both hooks.
150 A hook can be set into a state where incoming packets are always queued
155 A hook may supply overriding receive data and receive message functions,
156 which should be used for data and messages received through that hook
161 For example, connecting to the hook named
164 the node to start sending debugging information to that hook.
202 hook names as the destination address for the message (relative
205 node may simply specify (as a pointer in the code) the hook across which the
238 at that node through a particular hook (as opposed to having been directly
239 addressed using its ID or global name) then that hook is identified to the
285 or that requests coming in over a particular hook should be considered to
287 hook should always be queued, rather than delivered directly (often useful
393 .It Creation of a new hook
394 The hook is created and tentatively
396 used to describe this hook.
398 it needs, or may reject the connection, based on the name of the hook.
406 a node may decide whether to set a particular hook (or its peer) into
410 .It Destruction of a hook
414 of one hook may be an acceptable event while for another it
458 The node is notified on which hook the item has arrived,
508 flag in the flags word of the hook on which that data will arrive.
517 for data received on a particular hook, to simplify coding.
519 .Fn NG_HOOK_SET_RCVDATA hook fn
522 other than it will receive all (and only) packets from that hook.
563 If the message was delivered via a specific hook, that hook will
566 the message out another hook to that on which it arrived.
569 for messages received on a particular hook, to simplify coding.
571 .Fn NG_HOOK_SET_RCVMSG hook fn
574 other than it will receive all (and only) messages from that hook.
592 Node and hook names should be
597 with a node name or ID, followed by a colon, followed by a sequence of hook
601 A relative address includes only the sequence of hook names, implicitly
602 starting hook traversal at the local node.
642 reached it via its hook
660 used, the recipient is notified of the hook on which the
668 hook, with each node making
670 So when B receives a frame on hook
685 .Em "direct hook pointer"
762 is a function that will be called for each hook
764 .Fn fn hook arg
768 will be set to the hook at which the search was terminated.
774 their hook pointers.
778 The following properties are associated with a hook, and can be
781 .It A hook dependent opaque cookie
784 .Fn NG_HOOK_SET_PRIVATE hook value
786 .Fn NG_HOOK_PRIVATE hook
790 .Fn NG_HOOK_NODE hook
792 .It A peer hook Pq Vt hook_p
793 The other hook in this connected pair.
795 .Fn NG_HOOK_PEER hook
799 .Fn NG_HOOK_REF hook
801 .Fn NG_HOOK_UNREF hook
803 increment and decrement the hook reference count accordingly.
804 After decrement you should always assume the hook has been freed
808 .Fn NG_HOOK_SET_RCVDATA hook fn
810 .Fn NG_HOOK_SET_RCVMSG hook fn
816 messages received on the hook on which they are set.
823 Typically a node's private info contains a back-pointer to the node or hook
832 From a hook you can obtain the corresponding node, and from
1002 Connect to another node, using the supplied hook names on either end.
1005 supplied hook names.
1021 Ask the node to break a hook connection to one of its neighbours.
1201 hook from which it arrived.
1234 Has a hook for the encapsulated packets
1236 and one hook
1240 Has a hook for the encapsulated packets
1242 and one hook