CLAMLIGHT

basic idea: 
   * control screens remotely for lighting and display effects
   * screens are pure slaves
   * each screen independently controllable
   * v1: solid color expressed as RGB for whole screen
   * vN: various animations (flash, animated gf, &c)

architecture
   * each lamp announces who it is
   * polls a REST api to discover what it should do
   * periodic polling
   * use Comet later

URL Structure

   Slave

   request display:

     http://api.clamlight.com/<SESSION_ID>/lamp/<LAMP_ID>/status
     www.clamlight.com/api?session_id=<SESSION_ID>&lamp_id=<LAMP_ID>&action="status"
     returns json structure like:
     {"lamp_id": <LAMP_ID>, "active":"1" , "rgb":"#rrggbb"}

   Master

   request all status
     http://api.clamlight.com/<SESSION_ID>/controller/status
     www.clamlight.com/api?session_id=<SESSION_ID>&action="status"
     { "lamps" : [ { "lamp_id" : <LAMP_ID>, "active":1, "rgb":"#rrggbb"},... }

   set status
     http://api.clamlight.com/<SESSION_ID>/controller/setstatus
     POST like:
     {"lamp_id": <LAMP_ID>, "active":"1" , "rgb":"#rrggbb"}

     www.clamlight.com/api?session_id=<SESSION_ID>&lamp_id=<LAMP_ID>&action="setstatus"&rgb=#rrggbb

Next features
    save scene
     http://api.clamlight.com/<SESSION_ID>/controller/savescene
     POST like:
     {"savescene":<SCENE_NAME>}
    get available scenes
     GET http://api.clamlight.com/<SESSION_ID>/controller/getscenes
     {scenes: [ scenes] }

database schema
"lhf" stands for "Last Heard From"

SESSION_TABLE
session_id session_name session_lhf

LAMPS_TABLE
lamp_id session_id lamp_name lamp_rgb lamp_lhf

SCENES_TABLE
scene_id session_id scene_name 

SCENE_LAMPS_TABLE
scene_id session_id lamp_id lamp_rgb