##// END OF EJS Templates
Fixing messaging docs to reflect msg_type in header.
Brian E. Granger -
Show More
@@ -101,18 +101,18 b' generic structure::'
101 # collaborative settings where multiple users may be interacting with the
101 # collaborative settings where multiple users may be interacting with the
102 # same kernel simultaneously, so that frontends can label the various
102 # same kernel simultaneously, so that frontends can label the various
103 # messages in a meaningful way.
103 # messages in a meaningful way.
104 'header' : { 'msg_id' : uuid,
104 'header' : {
105 'username' : str,
105 'msg_id' : uuid,
106 'session' : uuid
106 'username' : str,
107 'session' : uuid
108 # All recognized message type strings are listed below.
109 'msg_type' : str,
107 },
110 },
108
111
109 # In a chain of messages, the header from the parent is copied so that
112 # In a chain of messages, the header from the parent is copied so that
110 # clients can track where messages come from.
113 # clients can track where messages come from.
111 'parent_header' : dict,
114 'parent_header' : dict,
112
115
113 # All recognized message type strings are listed below.
114 'msg_type' : str,
115
116 # The actual content of the message must be a dict, whose structure
116 # The actual content of the message must be a dict, whose structure
117 # depends on the message type.x
117 # depends on the message type.x
118 'content' : dict,
118 'content' : dict,
General Comments 0
You need to be logged in to leave comments. Login now