Update api

client/client.py

@@ -1,3 +1,4 @@
+#!/usr/bin/env python2.7
 # -*- coding: utf-8 -*-
 import socket, json, time
 import pygame
@@ -76,22 +77,22 @@ def handleControls(event, gameId):
 
 def main():
     gameInit = newGame()
-    gameId = gameInit['ID']
+    gameId = gameInit['id']
     up = gameInit
-    initSize=len(up['SNAKE'])
+    initSize=len(up['snake'])
     continuer = True
     
     while continuer:
-        afficher(ecran, up['SNAKE'], up['FOOD'])
+        afficher(ecran, up['snake'], up['food'])
-        ecran.blit(myfont.render('Score {}'.format(len(up['SNAKE'])-initSize), False, (0, 0, 0)),(0,0))
+        ecran.blit(myfont.render('Score {}'.format(len(up['snake'])-initSize), False, (0, 0, 0)),(0,0))
         for event in pygame.event.get():
             if event.type == pygame.QUIT:
                 continuer = False
             elif event.type == pygame.KEYDOWN:
                 updateTmp = handleControls(event, gameId)
                 print(updateTmp)
-                if updateTmp != None and 'TYPE' in updateTmp:
+                if updateTmp != None and 'type' in updateTmp:
-                    if updateTmp['TYPE'] != 'error':
+                    if updateTmp['type'] != 'error':
                         up = updateTmp
         time.sleep(0.3)
         pygame.display.flip()

doc/api.org

@@ -4,14 +4,10 @@
 #+LATEX_HEADER: \usepackage{fullpage}
 
 * General Description
-  - All transmissions will be based on TCP since:
+  - All transmissions will be based on UDP since latency is important
-    - Packet length are not fixed (large variance depending on the snake size and food)
+  - All UDP datagrams between *client and server* will contain _plain json data_
-    - Packet ordering is important (inverted request can compromise gameplay)
+  - All data should be sent in *one* datagram
-  - All TCP streams from *client to server* will:
+  - All utf-8 characters in UDP datagram are in lower case
-    - Contain _plain json data_
-    - Be terminated by an "#EOF" line (in order for the server to detect the end of the client request)
-  - All TCP stream from *server to client* will contains _plain json data_ (connection will be closed by the server
-    so, there is no need of "#EOF").
 * Communications 
 ** Initialisation
    1. Client sent:
@@ -19,7 +15,6 @@
         {
             "type": "new-game"
         }
-        #EOF
       #+END_SRC
    2. Server can reply:
       #+BEGIN_SRC json
@@ -40,7 +35,6 @@
              "game-id": 1,
              "direction": "left",
          }
-         #EOF
        #+END_SRC
     2. Then, server can reply:
        #+BEGIN_SRC json
@@ -60,7 +54,6 @@
              "game-id": 1,
              "direction": null
          }
-         #EOF
        #+END_SRC
     2. Server can reply:
        #+BEGIN_SRC json

server/api/api.lisp

@@ -43,8 +43,9 @@
     (let* ((game-id (create-game gm)))
       (let ((game-dump (dump gm game-id)))
         (setf (getf game-dump :game-over) :null) ; Define nil as null (for json)
+        (string-downcase
          (to-json
-       (append (list :type "state") game-dump))))))
+          (append (list :type "state") game-dump)))))))
 
 (defmethod handle-update ((api api) data)
   (with-slots (gm) api
@@ -54,8 +55,9 @@
       (if dir
           (refresh game :dir dir)
         (refresh game))
+      (string-downcase
        (to-json
-       (append (list :type "state") (dump gm game-id))))))
+        (append (list :type "state") (dump gm game-id)))))))
 
 
 (defmethod handle-request ((api api) request)