Difference between revisions of "Georg's Talk on Message routing"

Jump to navigation Jump to search

Georg's Talk on Message routing (view source)

Revision as of 21:37, 3 February 2018

938 bytes removed ,  21:37, 3 February 2018
no edit summary
Line 1: Line 1:
See: [[Minutes_of_the_2018_Summit:_Day_one]]
= Georg's Talk on Message routing =


The slides from Ge0rG's talk: https://op-co.de/tmp/whats-wrong-with-xmpp-2017.pdf
The slides from Ge0rG's talk: https://op-co.de/tmp/whats-wrong-with-xmpp-2017.pdf
Line 43: Line 43:


To cover the gap of offline clients, we've implemented MAM. When you reconnect to the server, you can query the server for archived messages.
To cover the gap of offline clients, we've implemented MAM. When you reconnect to the server, you can query the server for archived messages.
{|
| -----------
| ----------------
| -----------------
| ----------------
| -----------------
|-
| TYPE
| TO BARE/ONLINE
| TO BARE/OFFLINE
| TO FULL/ONLINE
| TO FULL/OFFLINE
|-
| -----------
| ----------------
| -----------------
| ----------------
| -----------------
|-
| chat
| most available
| store/ERROR
| deliver
| store /m.-a
|-
| normal
| most available
| store/ERROR
| deliver
| ignore/error(*)
|-
| headline
| non-negative
| ignore
| deliver
| ignore/error
|-
| groupchat
| error
| error
| deliver
| IGNORE/error
|-
| error
| ignore
| ignore
| deliver
| ignore
|-
| -----------
| ----------------
| -----------------
| ----------------
| -----------------
|}
Top table is from two RFCs. Caps ones are erroneous.
"most available" = implementation defined. "non-negative presence" - can be none, one or any subset of clients
* *ejabberd: "most available" because it broke some clients


<span id="Message type problems"></span>'''Message type problems'''
<span id="Message type problems"></span>'''Message type problems'''
Jcbrand
181

edits

Retrieved from "https://wiki.xmpp.org/web/Special:MobileDiff/9985"

Navigation menu