Clj-symphony 1.0.0
Released under the Apache License, Version 2.0
A Clojure wrapper around the symphony-java-client library.
Installation
To install, add the following dependency to your project or build file:
[org.symphonyoss/clj-symphony "1.0.0"]
Namespaces
clj-symphony.chat
Operations related to ‘chats’. A ‘chat’ may contain 2 or more participants from 1 or 2 pods, and are different to rooms in that their membership is fixed at creation time.
Public variables and functions:
clj-symphony.chat
Operations related to ‘chats’. A ‘chat’ may contain 2 or more participants from 1 or 2 pods, and are different to rooms in that their membership is fixed at creation time.
Public variables and functions:
clj-symphony.connect
Operations related to connections to a Symphony pod.
Public variables and functions:
clj-symphony.connect
Operations related to connections to a Symphony pod.
Public variables and functions:
clj-symphony.message
Operations related to MessageMLv2 messages, which combine one or more of:
Public variables and functions:
clj-symphony.message
Operations related to MessageMLv2 messages, which combine one or more of:
Public variables and functions:
clj-symphony.room
Operations related to ‘rooms’. A ‘room’ is a named chat containing 1 or more participants from 1 or 2 pods.
clj-symphony.room
Operations related to ‘rooms’. A ‘room’ is a named chat containing 1 or more participants from 1 or 2 pods.
clj-symphony.stream
Operations related to ‘streams’. A ‘stream’ is the generic term for any kind of message channel in the Symphony platform, and comes in one of several flavours:
Public variables and functions:
clj-symphony.stream
Operations related to ‘streams’. A ‘stream’ is the generic term for any kind of message channel in the Symphony platform, and comes in one of several flavours:
Public variables and functions:
clj-symphony.user
Operations related to users. A user can be either a human or a service account (bot). Users can be identified in 3 separate ways:
Public variables and functions:
clj-symphony.user
Operations related to users. A user can be either a human or a service account (bot). Users can be identified in 3 separate ways:
Public variables and functions:
clj-symphony.user-connection
Operations related to user connections and requests for those connections. In Symphony, a user connection is an explicitly established relationship between users in different pods.
Public variables and functions:
- accept-all-connection-requests!
- accept-connection-request!
- accepted-requests
- accepted-requestsobjs
- incoming-requests
- incoming-requestsobjs
- pending-requests
- pending-requestsobjs
- reject-all-connection-requests!
- reject-connection-request!
- rejected-requests
- rejected-requestsobjs
- send-connection-request!
- user-connection-states
- user-connections
- user-connectionsobjs
- userconnectionobj->map
clj-symphony.user-connection
Operations related to user connections and requests for those connections. In Symphony, a user connection is an explicitly established relationship between users in different pods.
Public variables and functions:
- accept-all-connection-requests!
- accept-connection-request!
- accepted-requests
- accepted-requestsobjs
- incoming-requests
- incoming-requestsobjs
- pending-requests
- pending-requestsobjs
- reject-all-connection-requests!
- reject-connection-request!
- rejected-requests
- rejected-requestsobjs
- send-connection-request!
- user-connection-states
- user-connections
- user-connectionsobjs
- userconnectionobj->map