criticism of "id" was inaccurate. fixed.

This commit is contained in:
psyc://psyced.org/~lynX 2012-05-06 15:39:02 +02:00
parent 975a3cdd99
commit 352575e329
2 changed files with 8 additions and 6 deletions

View File

@ -97,11 +97,14 @@ for future projects:
#+INCLUDE: packets/chat_msg.json src js #+INCLUDE: packets/chat_msg.json src js
#+INCLUDE: packets/chat_msg.psyc src psyc #+INCLUDE: packets/chat_msg.psyc src psyc
Why PSYC doesn't have an id? Because packet counting from contexts # Why PSYC doesn't have an id? Because for most operations they aren't
and circuits is automatic: The packet already has a number just by # needed: PSYC has automatic packet counting from contexts and circuits.
being there. # Therefore, the packet already has an id just by being there.
# Should you want to tag a packet anyway, you can do so by adding a _tag.
#
# Update: XMPP doesn't *need* to have an id there, so we can just remove it.
Also, PSYC by default doesn't mention a "resource" in XMPP terms, Little difference: PSYC by default doesn't mention a "resource" in XMPP terms,
instead it allows for more addressing schemes than just PSYC. instead it allows for more addressing schemes than just PSYC.
** A new status updated activity ** A new status updated activity

View File

@ -1,4 +1,3 @@
<message from='juliet@example.com/balcony' to='romeo@example.net' <message from='juliet@example.com/balcony' to='romeo@example.net' type='chat'>
id='ktx72v49' type='chat'>
<body>Art thou not Romeo, and a Montague?</body> <body>Art thou not Romeo, and a Montague?</body>
</message> </message>