pentominos:artefact
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
pentominos:artefact [2009/04/07 10:01] – deva | pentominos:artefact [2010/03/31 12:24] (current) – deva | ||
---|---|---|---|
Line 1: | Line 1: | ||
======Artefact====== | ======Artefact====== | ||
+ | [[LUA Scripts]] | ||
====Reply problems==== | ====Reply problems==== | ||
Line 8: | Line 9: | ||
* We need a status message system that can contain several status messages. | * 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). | * 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? | + | 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' | ||
+ | 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==== | ====The data transportation path==== | ||
Line 110: | Line 119: | ||
* {{: | * {{: | ||
* {{: | * {{: | ||
+ | * {{: | ||
pentominos/artefact.1239091275.txt.gz · Last modified: 2009/04/07 10:01 by deva