preparing for 1.15.1 releasev1-15-1

1 files changed, 6 insertions, 2 deletions

diff --git a/doc/features.html b/doc/features.html
index 7a690ae7..611e8403 100644
--- a/doc/features.html
+++ b/doc/features.html
@@ -50,8 +50,12 @@ at some time moved back to the sourceforge tracker.</p>
  <li>create a plug-in-interface<li>implement native email-functionality in 
 	selector (probably best done as a plug-in)<li>port it to more *nix variants 
 	(eg AIX and HP UX) - this needs volunteers with access to those machines and 
-	knowledge<li>support for native SSL enryption of plain tcp syslog sessions. This will 
-	most probably happen based on syslog-transport-tls.<li>even more enhanced multi-threading<li>pcre filtering - maybe (depending on feedback)&nbsp; - simple regex already 
+	knowledge<li>provide an on-disk queue for syslog messages; should be 
+	combined with reliable delivery to the next hop<li>support for native SSL enryption of plain tcp syslog sessions. This will 
+	most probably happen based on syslog-transport-tls.<li>even more enhanced multi-threading, 
+	with a message queue for each selector line (when implementing this, search 
+	for CHECKMULTIQUEUE comments in the source - they already contain hints of 
+	what to look at).<li>pcre filtering - maybe (depending on feedback)&nbsp; - simple regex already 
 	partly added. So far, this seems sufficient so that there is no urgent<li>support for
	<a href="http://www.monitorware.com/Common/en/glossary/rfc3195.php">RFC 3195</a> 
	as a sender - this is currently unlikely to happen, because there is no real 
 	demand for it. Any work on RFC 3195 has been suspend until we see some real 
 	interest in it.&nbsp; It is probably much better to use TCP-based syslog,