SMP server:

• handshake:
  • request and optionally pass client certificate to SMP server
  • SMP handshake with additional server response 8558f2f
  • get/create service record in handshake (currently, there is no database access in handshake, probably should be done via hook).
• verification
  • validate that command is allowed for service/role combination 9734edc
  • verify service signature 9734edc
• process server commands:
  • associate messaging service ID with queue
    • NEW command
    • SUB command (change response to SOK in all cases)
    • NSUB command (change response to SOK)
  • process SSUB command
  • process NSSUB command
  • process subscribed client/service changes in serverThread
• deliver events to connected service, based on associated service ID:
  • messages
  • notifications
  • DELD
  • END to individually subscribed connections when service subscribes, and vice versa
• statistics
  • encode/decode
  • include in prometheus
• storage
  • stm
  • postgres

Notification server:

• initial subscription:
  • handover to service (association).
  • re-handover if service ID changes in handshake or service becomes unavailable.
  • service subscription for queues that have the same service ID as in handshake.
• service subscriptions workers in "small agent"
• create association with service ID in CASubscribed
• additional "small agent" events when service subscriptions succeed/end
• prometheus: track counts of subscribed queues in service subscriptions

Chat Agent:

• network setting to create certificates for the service, one per user+server combination.
• send certificate in TLS/SMP handshakes, store service ID.
• create association:
  • creating queue (newRcvQueue) when creating connection, joining and switching connections
  • response to subscriptions.
• return service association in async responses.
• service subscription agent API - should accept user and service ID, respond with error if handshake reports different service ID, so that chat can re-handover.
• account for service subscriptions in agent stats

Chat Core:

• probably, should store service association on connections too.
• maintain the set of subscribed services, report them to UI, so that spinners disappear.
• initial subscription - read services for all connections, read unassociated connections only to handover.
• re-handover on agent error (if service ID changes).