From 63406665e139e0e4684d745aa3ebe168f649b269 Mon Sep 17 00:00:00 2001 From: Moon Wang Date: Tue, 18 Feb 2020 20:39:41 +0800 Subject: [PATCH] Update streaming.md --- developing-with-nats-streaming/streaming.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/developing-with-nats-streaming/streaming.md b/developing-with-nats-streaming/streaming.md index b24eb1b..58ce6c1 100644 --- a/developing-with-nats-streaming/streaming.md +++ b/developing-with-nats-streaming/streaming.md @@ -97,8 +97,6 @@ NATS Streaming supports several types of subscriptions: * Queue * Durable/Queue -Regular subscriptions pick the location of their channel position on creation and it is stored in the subscriber while the subscriber is active. Durable subscriptions store their position in the streaming server. Queue subscriptions share a channel position. Durable/Queue subscriptions share a channel position stored in the server. All subscriptions can be configured with a starting position, but only new durable subscriptions and new regular subscriptions respect the request. - All subscriptions define their position on creation. Regular subscriptions lose their position if the application crashes, the app disconnects or they unsubscribe. Durable subscriptions maintain their position through disconnect, subscriber close, but not through unsubscribe. The position on reconnect comes from the server not the options in both cases. Queue subscriptions share a position. Regular queue subscriptions lose their position on the last disconnect/unsubscribe. Durable queue subscriptions maintain their position through disconnect, but not through the last unsubscribe. Positions provided in options are ignored after the position is set. ## Acknowledgements