#include <nats.h>
|
| int64_t | Expires |
| | Expiration of the request, expressed in nanoseconds.
|
| |
| int | Batch |
| | Maximum number of messages to be received (see MaxBytes)
|
| |
| int64_t | MaxBytes |
| | Maximum bytes for the request (request complete based on whichever Batch or MaxBytes comes first)
|
| |
| bool | NoWait |
| | Will not wait if the request cannot be completed.
|
| |
| int64_t | Heartbeat |
| | Have server sends heartbeats to help detect communication failures.
|
| |
| int64_t | MinPending |
| |
| int64_t | MinAckPending |
| |
| const char * | ID |
| |
| const char * | Group |
| |
Options for the natsSubscription_FetchRequest() call, which is similar to natsSubscription_Fetch() but gives more control in the configuration of the fetch.
◆ Expires
| int64_t jsFetchRequest::Expires |
◆ Batch
| int jsFetchRequest::Batch |
◆ MaxBytes
| int64_t jsFetchRequest::MaxBytes |
◆ NoWait
| bool jsFetchRequest::NoWait |
◆ Heartbeat
| int64_t jsFetchRequest::Heartbeat |
◆ MinPending
| int64_t jsFetchRequest::MinPending |
◆ MinAckPending
| int64_t jsFetchRequest::MinAckPending |
◆ ID
| const char* jsFetchRequest::ID |
the "pinned" ID of this subscription, if any; to use with the "pinned_client" priority policy
◆ Group
| const char* jsFetchRequest::Group |
The documentation for this struct was generated from the following file: