Protocols

Each meeting may have a list of associated formats, describing details about the meeting.

This defines the meeting’s physical location component.

This is one of the venues in a virtual meeting specifier.

This defines the meeting’s virtual component (if any).

Each meeting instance will present itself as conforming to this protocol.

Each meeting is given/managed by an organization (AA, NA, etc.). This defines the associated organization.

We define this as applied to classes, so it can be overloaded/ridden. The idea is to define a specific organization, with a custom transport, for each server.

This defines a protocol, that describes a simple extraInfo String, allowing conformant types to store string information.

This defines a protocol, that declares a simple extraInfo String, allowing conformant types to store string information.

This defines a protocol, containing a “found set” of meeting data.

It is defined for a class, so it can be referenced (possibly weakly), in order to avoid data duplication.

This defines the requirements for the main SDK instance.

This defines the requirements for an instance of a data parser for the transport.

This is supplied to a transport instance, and is used to form the searh “stimulus” commands, to be sent to the server.

This defines requirements for a loosely-coupled transport layer.