From b9dc14cb020bdec5ce0fbace2fadce19c98d0501 Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Tue, 10 Jul 2007 12:46:46 +0000 Subject: preparing for 1.15.1 release --- doc/features.html | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) (limited to 'doc/features.html') 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.

  • create a plug-in-interface
  • implement native email-functionality in selector (probably best done as a plug-in)
  • port it to more *nix variants (eg AIX and HP UX) - this needs volunteers with access to those machines and - knowledge
  • support for native SSL enryption of plain tcp syslog sessions. This will - most probably happen based on syslog-transport-tls.
  • even more enhanced multi-threading
  • pcre filtering - maybe (depending on feedback)  - simple regex already + knowledge
  • provide an on-disk queue for syslog messages; should be + combined with reliable delivery to the next hop
  • support for native SSL enryption of plain tcp syslog sessions. This will + most probably happen based on syslog-transport-tls.
  • 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).
  • pcre filtering - maybe (depending on feedback)  - simple regex already partly added. So far, this seems sufficient so that there is no urgent
  • support for RFC 3195 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.  It is probably much better to use TCP-based syslog, -- cgit