Browse files

Fixing messaging docs to reflect msg_type in header.

  • Loading branch information...
1 parent 88dae27 commit 12aef932a5a6cbac840a3cdcef02ef95de1b77e3 @ellisonbg committed Jul 14, 2011
Showing with 6 additions and 6 deletions.
  1. +6 −6 docs/source/development/messaging.txt
View
12 docs/source/development/messaging.txt
@@ -101,18 +101,18 @@ generic structure::
# collaborative settings where multiple users may be interacting with the
# same kernel simultaneously, so that frontends can label the various
# messages in a meaningful way.
- 'header' : { 'msg_id' : uuid,
- 'username' : str,
- 'session' : uuid
+ 'header' : {
+ 'msg_id' : uuid,
+ 'username' : str,
+ 'session' : uuid
+ # All recognized message type strings are listed below.
+ 'msg_type' : str,
},
# In a chain of messages, the header from the parent is copied so that
# clients can track where messages come from.
'parent_header' : dict,
- # All recognized message type strings are listed below.
- 'msg_type' : str,
-
# The actual content of the message must be a dict, whose structure
# depends on the message type.x
'content' : dict,

0 comments on commit 12aef93

Please sign in to comment.