Differences

This shows you the differences between two versions of the page.

--- pentominos:artefact [2009/02/26 09:48] – deva
+++ pentominos:artefact [2010/03/31 12:24] (current) – deva
@@ Line 1: / Line 1: @@
 ======Artefact======
+[[LUA Scripts]]
+====Reply problems====
+The outline of the problem is, "when is it possible to return status information to the client, and when is it actually needed?".
+  * If the transaction contains a single data entry, the server should respond with the status of the insertion of that entry.
+  * If the transaction contains several data entries, the server should respond with the status of the insertions of these entries.
+    * We need a way to map a status message to an entry.
+    * We need a status message system that can contain several status messages.
+  * If the transaction contains both data entry (or entries) and query (or queries), the server should respond with the status of the insertions as well as the answer to and status of query (queries).
+Should (can) the status message be treated as just another query?\\
+\\
+===Proposition===
+Data and Query cannot be located in the same transaction.
+Query works as it does now (it reply's with the result of the query in the requested reply-language).\\
+Data returns a (using the same result structure as the queries) series of status messages, each mapping to a Data section by number starting from 0.\\
+Therefore the order in which the Data segments are handled matter!\\
+The reply language of the Data transaction will be the XML language. This might be user defined at some later point.
+The Queries can be extended to also include a status message list in the reply.
 ====The data transportation path====
 When an apparatus is connected the following must be crafted:
   * Feed parser so file and conf.
-  * Artefact validator / identifier.
+  * Artefact classifier.
     * Makes superficial parsing of the data to identify whether the data is valid.
     * Figure out what classes are contained in the data, and report this.
-  * Artefact interpretation
-    * Parses and interprets the data, translating it into some output language (eg. xml)
-  (data, class) => [lua] Parser -> [lua] Interpretation -> [lua/c] Tree structure -> [c] language filter -> network
+  (data) => network -> [lua] Parser -> [lua] Classifier (data, classes) -> [c] Store (db/disk)
+  * Artefact interpreter.
+    * Parses and interprets the data, translating it into an internal tree structure.
+  (data, class) => [lua] Parser -> [lua] Interpretation -> [lua/c] Tree structure -> [c] Pretty printer -> network
+===Template code===
+<code lua>
+--
+-- Read the data from <filename> and determ which classes it contains.
+--
+-- The following functions are available in the classify function:
+--    - addClass(classname)
+--          Mark data content as classname.
+--    - invalidData(errormsg)
+--          Report that the data is invalid.
+function classify(filename)
+  -- Load data from file
+  data = loadDataFromFile(filename);
+  -- ID has to equal NIDEK/
+end
+--
+-- Interpret data in <filename> creating a tree structure of groups. Each group
+-- contains values determed by the interpreter.
+--
+-- The following functions are available in the interpret function:
+--    - addGroup(parent, groupname) // Parent can be 0 if root
+--          Creates a new group with a groupname refering to a parent group.
+--          A value of 0 is allowed the group does not have any parents (ie. it is root).
+--          The function returns a group descriptor refering to the group.
+--    - addValue(groupdescriptor, valuename, value)
+--          Adds a value with key valuename to a group refered to by groupdescriptor.
+-- interpret() must return the root of the created tree structure.
+function interpret(filename)
+end
+function loadDataFromFile(filename)
+  local file = assert(io.open(filename))
+  local data = f:read("*all")
+  f.close()
+  return data;
+end
+</code>
 ====Patient registration====
@@ Line 27: / Line 90: @@
 A server listen will run in a read loop until the client terminates the connection.\\
 The server must reply to all request with an answer, no matter if the preceding processing went well or not.
 ====The client====
@@ Line 36: / Line 100: @@
 Each LUA program must run in an infinite loop, terminating only when the function stop() returns true, and it must not hang waiting on read, but rather have a time-out, and loop again.
-[[pentominos:client]]
+[[pentominos:feed]]
@@ Line 55: / Line 119: @@
   * {{:check.png}} Replace xerces-c with eXpat.
   * {{:uncheck.png}} Make SQL comm functions for the LUA programs return all results and not just the first one.
+  * {{:uncheck.png}} Make all use of time (struct time_t and postgresql timestamps) [[http://en.wikipedia.org/wiki/Year_2038_problem|Y2K38]] safe.