Lines Matching full:frame

2  * dnstap/dnstap_fstrm.h - Frame Streams protocol for dnstap
40  * Definitions for the Frame Streams data transport protocol for
47 /* Frame Streams data transfer protocol encode for DNSTAP messages.
54  * The Frame Streams can be unidirectional or bi-directional.
55  * bi-directional streams use control frame types READY, ACCEPT and FINISH.
56  * uni-directional streams use control frame types START and STOP.
57  * unknown control frame types should be ignored by the receiver, they
58  * do not change the data frame encoding.
63  * The uni-directional control frames have one start and one stop frame,
64  * before and after the data.  The start frame can have a content type.
69  * signals the presence of a control frame.
71  * a control frame consists of 0 value in 4byte bigendian, this is really
72  * the data frame length, with 0 the escape sequence that indicates one
73  * control frame follows.
74  * Then, 4byte bigendian, length of the control frame message.
75  * Then, the control frame payload (of that length). with in it:
84  * control frame max frame length 512 (excludes the 0-escape and control
85  * frame length bytes).
93  * client waits for FINISH frame.
97 /** max length of Frame Streams content type field string */
99 /** control frame value to denote the control frame ACCEPT */
101 /** control frame value to denote the control frame START */
103 /** control frame value to denote the control frame STOP */
105 /** control frame value to denote the control frame READY */
107 /** control frame value to denote the control frame FINISH */
112 /** the content type for DNSTAP frame streams */
116  * This creates an FSTRM control frame of type START.
119  * 	"protobuf:dnstap.Dnstap", for a dnstap frame stream.
123  * a control frame.  The buffer should be sent without preceding it with
126  * the zero control indicator can be included before the control frame length.
131  * This creates an FSTRM control frame of type READY.
134  * 	"protobuf:dnstap.Dnstap", for a dnstap frame stream.
138  * a control frame.  The buffer should be sent without preceding it with
141  * the zero control indicator can be included before the control frame length.
146  * This creates an FSTRM control frame of type STOP.
150  * a control frame.  The buffer should be sent without preceding it with
153  * the zero control indicator can be included before the control frame length.
158  * This creates an FSTRM control frame of type ACCEPT.
164  * a control frame.  The buffer should be sent without preceding it with
167  * the zero control indicator can be included before the control frame length.
172  * This creates an FSTRM control frame of type FINISH.
176  * a control frame.  The buffer should be sent without preceding it with
179  * the zero control indicator can be included before the control frame length.