You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by ol...@apache.org on 2020/09/28 11:37:48 UTC
[sling-org-apache-sling-clam] 02/02: add ClamEventsServlet and
MailSendingScanResultHandler
This is an automated email from the ASF dual-hosted git repository.
olli pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-org-apache-sling-clam.git
commit a42594b0921aa9ec1918c62f79e1223577b2ce9e
Author: Oliver Lietz <ol...@apache.org>
AuthorDate: Mon Sep 28 13:37:19 2020 +0200
add ClamEventsServlet and MailSendingScanResultHandler
---
README.md | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/README.md b/README.md
index 7002b7c..d7373ec 100644
--- a/README.md
+++ b/README.md
@@ -27,8 +27,12 @@ The service requires read-only access to all paths to be scanned which can be al
## Handling of scan results
+`ClamEventsServlet` publishes scan results as [Server-Sent Events](https://html.spec.whatwg.org/multipage/server-sent-events.html) via [HTTP](#http-api).
+
`EventPublishingScanResultHandler` publishes scan results via OSGi Event Admin Service.
+`MailSendingScanResultHandler` sends scan results as mails via [Sling Commons Messaging Mail](https://github.com/apache/sling-org-apache-sling-commons-messaging-mail).
+
`ResourcePersistingScanResultHandler` persists scan results via ResourceResolver in JCR. The result handler requires write access to a configurable root path for subservice `result-writer`.