Content deleted Content added
Melonkelon (talk | contribs) |
Logfreak4712 (talk | contribs) m direct link to TCP article, linked to rsyslog article |
||
Line 2:
==Overview==
RELP uses [[Transmission Control Protocol|TCP]] for message transmission. This provides basic protection against message loss, but does not guarantee delivery under all circumstances. When a connection is aborted, it cannot reliably detected if the last messages sent have actually reached their destination.<ref>{{cite web |url=http://blog.gerhards.net/2008/05/why-you-cant-build-reliable-tcp.html |date=2008-05-29 |title=Why you can't build a reliable TCP protocol without app-level acks |accessdate=2013-05-06}}</ref> Contrary to the syslog protocol, RELP works with a backchannel, over which information of messages processed by the receiver is conveyed back to the sender. This enables RELP to always know which messages have been properly received, even in the case of a connection abort.
==History==
Line 18:
* librelp - the original C RELP library
* [[rsyslog]]
* MonitorWare (Windows)
* logstash
| |||