aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorfriendica <info@friendica.com>2012-06-18 21:13:36 -0700
committerfriendica <info@friendica.com>2012-06-18 21:13:36 -0700
commit9dc51113477e315470c37e0f81728e91575a3963 (patch)
tree441d551a53f989dfaab64d3c6c3e683149fabf19
parente9aba87d76d44cf99db7666aa1bbb96489c3a04d (diff)
downloadvolse-hubzilla-9dc51113477e315470c37e0f81728e91575a3963.tar.gz
volse-hubzilla-9dc51113477e315470c37e0f81728e91575a3963.tar.bz2
volse-hubzilla-9dc51113477e315470c37e0f81728e91575a3963.zip
a bit more description of message passing
-rw-r--r--spec/zot-2012.txt6
1 files changed, 6 insertions, 0 deletions
diff --git a/spec/zot-2012.txt b/spec/zot-2012.txt
index b223a27ea..3b8d3272d 100644
--- a/spec/zot-2012.txt
+++ b/spec/zot-2012.txt
@@ -135,6 +135,12 @@ Returns:
Message
-------
+Passing messages is done asynchronously. This may (potentially) relieve a lot of the burden of distribution from the posting site. If you're on site 'A' and make a post, site 'A' just contacts any downstream sites and informs them that there is new content (via a $post_id). The downstream site initiates the actual data transfer.
+
+
+
+
+
POST https://example.com/post
{