xpra icon
Bug tracker and wiki

Changes between Version 8 and Version 9 of NetworkProtocol


Ignore:
Timestamp:
03/28/14 12:39:41 (6 years ago)
Author:
Antoine Martin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NetworkProtocol

    v8 v9  
    11= Network Protocol =
     2
     3{{{#!div class="box"
     4== Introduction ==
    25
    36This page documents the types of messages that the client and server can exchange.
    47For the actual network connection see [/wiki/Network] and for the encoding and compression of the messages see [/wiki/PacketEncoding].
    5 The most important packet is the first one sent, the {{{hello}}} packet, since it contains "capabilities" which determines what packets and features are supported by the other end.
     8[[BR]]
     9The most important packet is the first one sent, the {{{hello}}} packet, since it contains "capabilities" which determines what packets and features are supported by the other end. In a lot of cases, a client which does not implement all the features ''should'' disable the capability rather than ignoring the corresponding packets.
     10
     11[[BR]]
     12The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this document are to be interpreted as described in [https://www.ietf.org/rfc/rfc2119.txt RFC 2119].
     13}}}
    614
    715
     
    1927||= Packet Type =||= Arguments =||= Purpose =||= Actions Required =||= Client Capability Required =||
    2028||{{{startup-complete}}}||none||notifies the client that all the windows have been sent||none||{{{notify-startup-complete}}}||
    21 ||{{{new-window}}} and {{{new-override-redirect}}}||many||tells the client about a new regular window or override-redirect window||the client ''should'' show the new window, it should eventually send a {{{map-window}}} packet with the location of the window||none||
     29||{{{new-window}}} and [[BR]] {{{new-override-redirect}}}||many||tells the client about a new regular window or override-redirect window||the client ''should'' show the new window, it should eventually send a {{{map-window}}} packet with the location of the window||none||
    2230||{{{new-tray}}}||many||tells the client about a new tray window||the client ''should'' show the new system tray||{{{system_tray}}}||
    2331||{{{raise-window}}}||window ID||the window ''should'' be raised||the client may or may not honour the request to raise the window||{{{window.raise}}}||
    24 ||{{{window-move-resize}}}||window ID, new position and size||honour applications that request the window to be moved and resized||the client should move and resize the window||{{{server-window-move-resize}}}||
    25 ||{{{window-resized}}}||window ID and new size||the client should move and resize the window||{{{server-window-resize}}}||
     32||{{{window-move-resize}}}||window ID, new position and size||honour applications that request the window to be moved and resized||the client ''should'' move and resize the window||{{{server-window-move-resize}}}||
     33||{{{window-resized}}}||window ID and new size||honour applications that request the window to be resized - this is only a deprecated fallback for {{{window-move-resize}}}||the client ''should'' move and resize the window||{{{server-window-resize}}}||
     34||{{{cursor}}}||the cursor data (see code for details)||honour applications that request a different cursor||the client ''should'' display the new cursor immediately||{{{cursors}}}||
     35||{{{bell}}}||the bell sound definition (see code for details)||honour applications requesting the bell to ring||the client ''should'' ring the "bell" or its equivallent||{{{bell}}}||
     36||{{{notify_show}}}||notification ID, message, etc||honour applications which request that a notification be shown to the user||the client ''should'' show the notification||{{{notifications}}}||