X-Git-Url: https://git.mxchange.org/?a=blobdiff_plain;f=doc%2FMessage-Flow.md;h=e9679856953c1e3677482bd442bbdffa379355e6;hb=90368d7484470f2b4c04e11f550f1cf92afa7808;hp=9a6785d5992f1eea85023d0fce62011b309055e9;hpb=76ca015497d98b99536223909a8ba414766579ab;p=friendica.git

diff --git a/doc/Message-Flow.md b/doc/Message-Flow.md
index 9a6785d599..e967985695 100644
--- a/doc/Message-Flow.md
+++ b/doc/Message-Flow.md
@@ -4,9 +4,7 @@ Friendica Message Flow
 This page documents some of the details of how messages get from one person to another in the Friendica network.
 There are multiple paths, using multiple protocols and message formats.
 
-Those attempting to understand these message flows should become familiar with (at the minimum) the [DFRN protocol document](https://github.com/friendica/friendica/blob/master/spec/dfrn2.pdf) and the message passing elements of the OStatus stack (salmon and Pubsubhubbub).
-
-Most message passing involves the file include/items.php, which has functions for several feed-related import/export activities. 
+Those attempting to understand these message flows should become familiar with (at the minimum) the [DFRN protocol document](https://github.com/friendica/friendica/blob/stable/spec/dfrn2.pdf) and the message passing elements of the OStatus stack (salmon and Pubsubhubbub).
 
 When a message is posted, all immediate deliveries to all networks are made using include/notifier.php, which chooses how (and to whom) to deliver the message.
 This file also invokes the local side of all deliveries including DFRN-notify.
@@ -19,7 +17,7 @@ Salmon notifications arrive via mod/salmon.php.
 
 Push (pubsubhubbub) feeds arrive via mod/pubsub.php
 
-DFRN-poll feed imports arrive via include/poller.php as a scheduled task, this implements the local side of the DFRN-poll protocol.  
+DFRN-poll feed imports arrive via src/Worker/OnePoll.php as a scheduled task, this implements the local side of the DFRN-poll protocol.
 
 ### Scenario #1. Bob posts a public status message
 
@@ -28,7 +26,7 @@ There are two paths it can take - as a bbcode path to DFRN clients, and converte
 When a PuSH hub is operational, dfrn-poll clients prefer to receive their information through the PuSH channel.
 They will fall back on a daily poll in case the hub has delivery issues (this is quite common when using the default Google reference hub).
 If there is no specified hub or hubs, DFRN clients will poll at a configurable (per-contact) rate at up to 5-minute intervals.
-Feeds retrieved via dfrn-poll are bbcode and may also contain private conversations which the poller has permissions to see. 
+Feeds retrieved via dfrn-poll are bbcode and may also contain private conversations which the worker has permissions to see.
 
 ### Scenario #2. Jack replies to Bob's public message. Jack is on the Friendica/DFRN network.