Attendees
...
Apologies
Agenda | Presenter | Duration | Discussion | ||
Authentication and Cross-BB Authorization | 20 minutes | Walk through key questions and requirements in this document: Authentication and Cross-BB Authorization Where should this be documented? Security spec or separate BB spec? Sreepathy: architecture of having a single application managing makes sense and covers the flows/approach that were outlined in his email | |||
PubSub/Rooms | 15 minutes | How should we define Rooms – are they oriented around Event Types or more broadly? With many providers, topic is global - this is the more common pattern for PubSub Aleksander proposes having a room with an owner and topics reside within that room. Key question: Does an owner own a topic (and define event types for that topic) or a room? Do users subscribe to topics or to rooms? Is there benefit for the extra layer for rooms? What is the difference between a topic and a room? What functionality does Room provide?
The spec should just outline the ability for an entity to create a topic with a schema that other users/entities can subscribe to. There may be multiple ways to implement.
| |||
Capabilities | 15 minutes | How should we define Capabilities? Document from Jaume: https://docs.google.com/presentation/d/11zg0PQQKbpWFxwAc_oK12iM83ax8hUpBqlJHwB-kLGk/edit#slide=id.g1ab9444641b_0_218PubSub/Rooms | |||
15 minutes | How should we define Rooms – are they oriented around Event Types or more broadly? Next steps/AOB | 5 minutes | Jukka will no longer be able to participate in architecture team - has other projects that require his time. What should we prioritize?
|
...