From b4ecd58b337192933fe73ff3f0a23d88b7a0cf74 Mon Sep 17 00:00:00 2001 From: Ginger Collison Date: Thu, 23 May 2019 13:01:24 -0500 Subject: [PATCH] Update subscriptions.md --- nats_streaming/channels/subscriptions/subscriptions.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/nats_streaming/channels/subscriptions/subscriptions.md b/nats_streaming/channels/subscriptions/subscriptions.md index 3fea537..78b173b 100644 --- a/nats_streaming/channels/subscriptions/subscriptions.md +++ b/nats_streaming/channels/subscriptions/subscriptions.md @@ -1,13 +1,11 @@ # Subscriptions -A client creates a subscription on a given channel. Remember, there is no support for wildcards, so a subscription is really tied to -one and only one channel. The server will maintain the subscription state on behalf of the client until the later closes the subscription (or its connection). +A client creates a subscription on a given channel. Remember, there is no support for wildcards, so a subscription is really tied to one and only one channel. The server will maintain the subscription state on behalf of the client until the later closes the subscription (or its connection). -If there are messages in the log for this channel, messages will be sent to the consumer when the subscription is created. The server will -send up to the maximum number of inflight messages as given by the client when creating the subscription. +If there are messages in the log for this channel, messages will be sent to the consumer when the subscription is created. The server will send up to the maximum number of inflight messages as given by the client when creating the subscription. When receiving ACKs from the consumer, the server will then deliver more messages, if more are available. A subscription can be created to start at any point in the message log, either by message sequence, or by time. -Following pages describe all types of subscription. \ No newline at end of file +Following pages describe all types of subscription.