How gauharb/sdp-asn3 works
This small Java example demonstrates bridge-based notifications. The demo client creates reminders or urgent alerts, selects a delivery channel, executes the notification, and checks the returned delivery string; it also switches a channel without replacing the notification object. Notification owns the bridge dispatch to channel formatting and delivery, while each notification subtype builds its own content and each channel formats and labels its result. The graph follows the README role map and sampled sources.
Main entry points: Main.java Demo runner · Notification.java Notification bridge · Channel.java Channel contract · EmailChannel.java Email channel
Components 9
Notification types
- Notification bridge
src/Notification.java - Reminder
src/Reminder.java - Urgent alert
src/UrgentAlert.java
Delivery channels
- Channel contract
src/Channel.java - Email channel
src/EmailChannel.java - SMS channel
src/SmsChannel.java - Push channel
src/PushChannel.java
Demo client
- Demo runner
src/Main.java
Other components
- CLI user
Connections 13
- CLI user → Demo runner: runs demo
ReadMe - Demo runner → Reminder: creates and executes
src/Main.java - Demo runner → Urgent alert: creates and executes
src/Main.java - Demo runner → Email channel: selects channel
src/Main.java - Demo runner → SMS channel: selects channel
src/Main.java - Demo runner → Push channel: selects channel
src/Main.java - Demo runner → Notification bridge: switches implementation
src/Main.java - Notification bridge → Reminder: dispatches content build
src/Notification.java - Notification bridge → Urgent alert: dispatches content build
src/Notification.java - Notification bridge → Channel contract: formats and delivers
src/Notification.java - Email channel → Channel contract: implements
src/EmailChannel.java - SMS channel → Channel contract: implements
src/SmsChannel.java - Push channel → Channel contract: implements
src/PushChannel.java