mirror of
https://github.com/taigrr/nats.docs
synced 2025-01-18 04:03:23 -08:00
Remove some trailing white space
This is to trigger a website rebuild. Doing something vaguely useful is a side-effect. While end-of-line whitespace has semantic value in Markdown, it's not doing anything when there's a paragraph break after it (AFAIK).
This commit is contained in:
parent
32e1e515dd
commit
b07b4d62ab
4
faq.md
4
faq.md
@ -131,8 +131,8 @@ No. As of `nats-server` v0.8.0, there is no hard limit on the maximum number of
|
|||||||
|
|
||||||
### Does NATS guarantee message delivery?
|
### Does NATS guarantee message delivery?
|
||||||
|
|
||||||
NATS Core Server, simply referred to as NATS Server, offers "at-most-once" delivery. This means messages are guaranteed to arrive intact, in order from a given publisher, but not across different publishers. NATS does everything required to remain available and provide a dial-tone. However, if a subscriber is problematic or goes offline it will not receive messages, as the basic NATS platform is a simple pub-sub transport system that offers only TCP reliability.
|
NATS Core Server, simply referred to as NATS Server, offers "at-most-once" delivery. This means messages are guaranteed to arrive intact, in order from a given publisher, but not across different publishers. NATS does everything required to remain available and provide a dial-tone. However, if a subscriber is problematic or goes offline it will not receive messages, as the basic NATS platform is a simple pub-sub transport system that offers only TCP reliability.
|
||||||
|
|
||||||
As of NATS Server 2.2, NATS JetStream offers persistence as "at-least-once" delivery. See the [JetStream](jetstream/jetstream.md) documentation for detailed information.
|
As of NATS Server 2.2, NATS JetStream offers persistence as "at-least-once" delivery. See the [JetStream](jetstream/jetstream.md) documentation for detailed information.
|
||||||
|
|
||||||
### Does NATS support replay/redelivery of historical data?
|
### Does NATS support replay/redelivery of historical data?
|
||||||
|
Loading…
x
Reference in New Issue
Block a user