<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -20,6 +20,7 @@ Protocol Definition
 -------------------
 
 session:
+	u8 (03)				-- send command to exchange headers
 	&quot;LRPC&quot;				-- &quot;lua remote function protocol&quot;
 	u8						-- protocol version
 	command, command, command, ...
@@ -28,7 +29,8 @@ session:
 command:
 	u8						-- command type (RPC_CMD_*)
 									 01 - function_call
-									 XX - extensible as required
+									 02 - get remote variable
+									 03 - exchange header credentials
 
 function_call:
 	string				-- name of function
@@ -52,18 +54,3 @@ var:
 string:	
 	u32						-- length
 	u8,u8,u8...		-- string bytes
-
-	
-Additional Notes
-----------------
-
-Protocol model from original implementer?:
-
-request:
-	&quot;LRPC&quot;		-- &quot;lua remote procedure call&quot;
-	u8 = 1		-- &quot;all lua function servers identify yourselves&quot;
-       
-reply:
-	&quot;LRPC&quot;		-- &quot;lua remote procedure call&quot;
-	u8 = 2		-- standard reply code
-	string		-- the name of this function server</diff>
      <filename>PROTOCOL</filename>
    </modified>
    <modified>
      <diff>@@ -1,10 +1,14 @@
 TODO
 ----
 
-rpc_on_error (HANDLE, func)   &lt;-- add option for handle 
+come up with cleaner approach towards getting remote variables
 
-pass user data to a remote function (or as return values)? the write()
-function apparently needs this
+__newindex implementation to set variables on remote side
+
+deal better with link level errors, especially for serial where minimal
+transmission guarantees are made
+
+rpc.on_error (HANDLE, func)   &lt;-- add option for handle 
 
 pass functions to a remote function (maybe so we can pass local callbacks
 to a remote function). thus we are tying together two function spaces?
@@ -45,10 +49,21 @@ async mode:
 	pass async flag in function call, so no return args passed
 	when reading old async function return values, handle old errors??
 
+OLD TODOS
+---------
+
+pass user data to a remote function (or as return values)? the write()
+function apparently needs this
 
 DONE
 ----
 
+abstract link/transport layer to allow different transports to be used
+
+implement serial support
+
+allow calling functions which are not globals (i.e. ones registered on tables)
+
 handle non-existance of the remote function. we need some convention around
 LRF_call ... or a &quot;verify existance of remote function&quot; function.
 </diff>
      <filename>TODO</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>8ddf0855d80b16ecea9f337b312862cebe13becb</id>
    </parent>
  </parents>
  <author>
    <name>James Snyder</name>
    <email>jbsnyder@fanplastic.org</email>
  </author>
  <url>http://github.com/jsnyder/luarpc/commit/7df1fd87ce90007945f5c031c8c7540297b365fa</url>
  <id>7df1fd87ce90007945f5c031c8c7540297b365fa</id>
  <committed-date>2009-06-08T11:16:41-07:00</committed-date>
  <authored-date>2009-06-08T11:16:41-07:00</authored-date>
  <message>Update notes about status.</message>
  <tree>6199824cea2ddaf7b2a6e3198fe90ec61e4a6b17</tree>
  <committer>
    <name>James Snyder</name>
    <email>jbsnyder@fanplastic.org</email>
  </committer>
</commit>
