#include <nds_iterate_handlers.hh>
- Note
- This will return data as it is available, without filling in gaps. It can handle offline nds2 requests, as long as the gaps for each channel are identical. This is much heaver weight than iterate_fast_handler.
◆ iterate_available_handler()
NDS::detail::iterate_available_handler::iterate_available_handler |
( |
buffer::gps_second_type |
gps_start, |
|
|
buffer::gps_second_type |
gps_stop, |
|
|
buffer::gps_second_type |
stride, |
|
|
const channel::channel_names_type & |
channel_names, |
|
|
std::shared_ptr< NDS::detail::conn_p_type > && |
parent |
|
) |
| |
|
inline |
◆ ~iterate_available_handler()
NDS::detail::iterate_available_handler::~iterate_available_handler |
( |
| ) |
|
|
overridedefault |
◆ has_next()
bool NDS::detail::iterate_available_handler::has_next |
( |
| ) |
|
|
inlineoverridevirtual |
◆ next()
void NDS::detail::iterate_available_handler::next |
( |
buffers_type & |
output | ) |
|
|
inlineoverridevirtual |
◆ setup_next_step()
◆ cur_gps_
buffer::gps_second_type NDS::detail::iterate_available_handler::cur_gps_ |
|
private |
◆ cur_segment_
◆ fragment_list_
◆ gps_start_
buffer::gps_second_type NDS::detail::iterate_available_handler::gps_start_ |
|
private |
◆ gps_stop_
buffer::gps_second_type NDS::detail::iterate_available_handler::gps_stop_ |
|
private |
◆ max_stride_
buffer::gps_second_type NDS::detail::iterate_available_handler::max_stride_ |
|
private |
◆ names_
channel::channel_names_type NDS::detail::iterate_available_handler::names_ |
|
private |
◆ next_entry_
buffers_type NDS::detail::iterate_available_handler::next_entry_ |
|
private |
The documentation for this class was generated from the following file: