The Pentominos project consists of several sub-projects, that all work together to produce a full circle of data gathering, data storage and data retrieval.
Here is a list of the current sub-projects:

• Artefact - The data storage server.
• Feed - A thin client data gathering application.
• Upload Server - Journal writer.
• Pidiod - The uid ⇒ patient ID mapper.
• Pidio - The uid ⇒ patient ID mapper client (numpad/rfid).

LUADataValidator
LUADataParser

When an apparatus is connected the following must be crafted:

• Feed parser so file and conf.
• Artefact validator / identifier.
  • 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

The system stores data. These data is connected to a patient ID, a timestamp, a location and an apparatus.
Getting the patient ID is a non-trivial task at best.
See the registration section for a description of the framework surrounding the registration system.

rfid project

All network communication are done via XML documents.
Every XML document is terminated by the zero character ('\0' in c/c++)
Sending the zero character to a process will reset it, and thereby cleaning up all mess made by illegal documents.
A connection can only be created in client-mode, and will exists as long as the client intends it to.
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 reads its config file, and forks for each config section it encounters.
Every fork handles a single apparatus according to the attached config section.
The main thread runs infinitely and makes sure to terminate all client forks upon termination.
Every client is connected physically to a port on the host computer, and a LUA program runs to determine whether data is ready to be read or not.
The LUA programs hereafter sends this data to the server indirectly through a number of exposed c methods.
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.

client

Problem: An apparatus produces more than one type of data, but stores all measured values in the same data block. How to make a query that will hit this multi-data block?
Solutions:

• Make the validator insert one entry in the db for each data type, referring to the same data block (file).
  • The data are only stored once in the file system.
  • We don't need to make drastic changes to the server code (or client for that matter).

• http://xerces.apache.org/xerces-c/

• Make SQL comm functions for the LUA programs (e.g. for the cpr server).
• Rewrite server to utilize read loop.
• Replace xerces-c with eXpat.
• Make SQL comm functions for the LUA programs return all results and not just the first one.