Skip to content

Support standalone signaling server for chat - #890

Merged
Ivansss merged 3 commits into
masterfrom
chat-standalone-signaling
Jun 15, 2018
Merged

Support standalone signaling server for chat#890
Ivansss merged 3 commits into
masterfrom
chat-standalone-signaling

Conversation

@fancycode

@fancycode fancycode commented May 9, 2018

Copy link
Copy Markdown
Member

Implements #624. Based on #887 which should be merged first.

@fancycode fancycode added feature: chat 💬 Chat and system messages feature: signaling 📶 Internal and external signaling backends labels May 9, 2018
@fancycode fancycode changed the title Support standalone signaling server for chat (#624) Support standalone signaling server for chat May 9, 2018
@fancycode

Copy link
Copy Markdown
Member Author

This is a first improvement in that the polling gets removed, the messages are still loaded from PHP.

In a future step, this could be changed further so that the messages are sent through the WebSocket and no more PHP calls are necessary (besides loading the initial list of past messages).

@nickvergessen nickvergessen added this to the 4.0 (Nextcloud 14) milestone May 11, 2018
This removes the long-polling against the PHP backend and instead sends an
event to all users in a room through the standalone signaling server to
notify that new chat messages exist.

Signed-off-by: Joachim Bauch <bauch@struktur.de>
Signed-off-by: Joachim Bauch <bauch@struktur.de>
Signed-off-by: Joachim Bauch <bauch@struktur.de>
@fancycode
fancycode changed the base branch from chat-signaling to master June 12, 2018 10:05
@fancycode
fancycode force-pushed the chat-standalone-signaling branch from 27d55af to 191075b Compare June 12, 2018 10:13
@Ivansss
Ivansss merged commit 22e8ca7 into master Jun 15, 2018
@Ivansss
Ivansss deleted the chat-standalone-signaling branch June 15, 2018 07:46
@nickvergessen

Copy link
Copy Markdown
Member

You guys forgot the backport label :(

@fancycode

Copy link
Copy Markdown
Member Author

This will also need a backport of #887 then.

@nickvergessen

Copy link
Copy Markdown
Member

And #398 :(

@fancycode

Copy link
Copy Markdown
Member Author

Btw, what are the guidelines for backporting issues? From what I understand from the past, only bug fixes should be backported but no new features.

@nickvergessen

Copy link
Copy Markdown
Member

In this app we backport everything which is not server-version dependent.
So that all features are always available in the latest supported server version (atm 13).

The diff between master + stable13 (or in the future stable14) should only be code that is necessary for server master, e.g. a lot of CSS changes are necessary and personal settings module was changed.

@fancycode

Copy link
Copy Markdown
Member Author

Ok, thanks for clarification. I'll add the backport-request label accordingly in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature: chat 💬 Chat and system messages feature: signaling 📶 Internal and external signaling backends

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants