Lines Matching +full:stream +full:- +full:mode

13 bytes). The BLOB transfer protocol has built-in recovery procedures for packet losses, and sets up
19 BLOB to be transferred in 10-15 minutes. However, network conditions, transfer capabilities and
52 The BLOB transfer protocol does not provide any built-in integrity checks, encryption or
58 ------
68 ------
72 mechanism for transferring chunks depends on the transfer mode.
74 When operating in Push BLOB Transfer Mode, the chunks are sent as unacknowledged packets from the
80 When operating in Pull BLOB Transfer Mode, the BLOB Transfer Server will request a small number of
92 In the BLOB Transfer models' APIs, the BLOB data handling is separated from the high-level transfer
95 itself is accessed through a *BLOB stream*.
97 The BLOB stream is comparable to a standard library file stream. Through opening, closing, reading
99 RAM, or on a peripheral. The BLOB stream is opened with an access mode (read or write) before it's
101 using the BLOB stream as an interface.
104 -----------
106 Before the BLOB is read or written, the stream is opened by calling its
108 stream is always opened in write mode, and when used with a BLOB Transfer Client, it's always opened
109 in read mode.
112 :c:member:`block_start <bt_mesh_blob_io.block_start>`. Then, depending on the access mode, the BLOB
113 stream's :c:member:`wr <bt_mesh_blob_io.wr>` or :c:member:`rd <bt_mesh_blob_io.rd>` callback is
116 stream is closed by calling :c:member:`close <bt_mesh_blob_io.close>`.
119 ---------------
121 The application may implement their own BLOB stream, or use the implementations provided by Zephyr:
152 BLOBs can be transferred using two transfer modes, Push BLOB Transfer Mode and Pull BLOB Transfer
153 Mode. In most cases, the transfer should be conducted in Push BLOB Transfer Mode.
155 In Push BLOB Transfer Mode, the send rate is controlled by the BLOB Transfer Client, which will push
156 all the chunks of each block without any high level flow control. Push BLOB Transfer Mode supports
157 any number of Target nodes, and should be the default transfer mode.
159 In Pull BLOB Transfer Mode, the BLOB Transfer Server will "pull" the chunks from the BLOB Transfer
160 Client at its own rate. Pull BLOB Transfer Mode can be conducted with multiple Target nodes, and is
162 in Pull BLOB Transfer Mode, the BLOB Transfer Server will request chunks from the BLOB Transfer