Changes between Version 6 and Version 7 of DataProtocol


Ignore:
Timestamp:
Jun 8, 2011 2:23:27 PM (13 years ago)
Author:
jherwitz
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DataProtocol

    v6 v7  
    11This page defines the Quagents3 datasream protocol.
    22
    3 The wiki:DataProtocol specifies the communication between the server and the client over the DataPort, port 6001. This communication takes the form of a constant datastream, which is used to maintain updated data on certain queries. The updates simplify client commands, as the client does not need to constantly poll the server for data using query commands.
     3The wiki:DataProtocol specifies the communication between the server and the client over the DataPort, port 6001. This communication takes the form of a constant datastream, which is used to maintain updated data on certain queries. The updates simplify client commands, as the client does not need to constantly poll the server for data using query commands. The protocol does not require commands, as wiki:ProtocolZero. The server only writes to the stream, and the client only reads from the stream.
    44
    55== Setup ==
    6 The server is notified of which queries need to be updated using a concatenation onto the "ready" command. The opcode and any parameters must be inserted followed by a ' ' for every desired updated command.
     6The server is notified of which queries need to be updated using a concatenation onto the "ready" command. The opcode and any parameters must be inserted followed by a ' ' for every desired updated command. This command is sent over the wiki:Protocol
    77
    88''Examples''
     
    1212{{{ready rf 9999 180 0}}}
    1313
     14== Specification ==
     15The datastream is a constant stream of updates sent from the server to the client over the DataPort. The protocol here is simple, a discrete update takes the form of
    1416
    15 == Datastream ==
     17{{{[OPCODE] [DATALIST]}}} where DATALIST is an arbitrary list of data, corresponding to each OPCODE query.