Notifications - Leipzig Hackathon 2017 breakout

Owned by Klaas Andries de Graaf
Nov 15, 2017
1 min read

Offline: Email notifications

Use-case scenario: students ask questions (comments on decks)

Use-case scenario: request access rights to decks - also send email to users that have been given access.

Email settings;

  • Direct (for actions → always, for any other notification → preference)
  • Daily digest (needs queuque - like cronjob)
  • Weekly digest (needs queuque - like cronjob)
  • Monthly digest(needs queuque - like cronjob)

Ali: dedicated service? - that runs once every day/week/month.

Queue service??

Needs flag in notification service - has been sent?

Better: do directly in notification service

Daily weekly cronjobs → call API function in notification service → sendDigestForUser/{id} every 5 seconds → function gathers notifications and sends email (depending on user preference → if weekly digest → skip user).

Have API function for directly sending emails, especially for notifications/events that require actions

Types of notifications:

1 → requires action

2 → activities: like slide/comments/etc..

Both have email (offline) + notification in notification panel (online)

Give link in email

Kostis: maybe create route in system that handles


Online: Notifications - make new notifications more visible


Real-time notifications: needed for real-time authoring.

Notifications not real-time currently

Have pull in notification panel → send request for new notifications every 1-10 seconds → not good for performance.

Ali: embed service in platform → has websocket → applies push-service. Iframe is not good.