Skip to content
Mike Douglass edited this page Mar 6, 2014 · 4 revisions

Introduction

The bedework notifier is intended to provide a notification service in addition to that provided by the calendar system and used by Apple and Apple compliant clients. It provides a means by which notification messages can be sent via email (or sms or some other means) for those who desire it.

Structure

The system consists of a central notification engine, inbound notification connectors and outbound adaptors.

Initially we will have one inbound connector - to bedework and one outbound adaptor - for email.

Inbound bedework

This will have its own configuration and JMX presence. It will be pointed at a folder in bedework accessible via CalDAV which it wil access through the public caldav interface - allowing us to do some funky authentication.

Inside that folder will be created links to the calendar home of users who wish to receive notifications. There will be one special link created for the notifications to users not on the system - usually invites to subscribe.

Setting up the system

Create the notification directory using the admin client - path should be the one set in the configs - something like /user/public-user/OutboundNotifications

Notes during development

Some of the changes made here need to be reflected back to the 3.10 system so that it can interact with the 4.0 notification service.

Authentication

The engine needs to authenticate with it's service. We should generate a special id/password combination that we can check for. We can call in via the unauthenticated service and check them there - or add a special auth module?