Use Perl instead of C for makeblob and makemetablob.

Begin coupling Formaline to thorn Announce.

Create stamp files that record which build and which simulation was
run in the output directory.

Begin implementing talking to an RDF server.

Determine the host name in Perl, which is more reliable.  (It is
complicated to find a good host name.)


git-svn-id: http://svn.cactuscode.org/arrangements/CactusUtils/Formaline/trunk@75 83718e91-0e4f-0410-abf4-91180603181f

1 files changed, 20 insertions, 2 deletions

diff --git a/README b/README
index d071c92..fa5c662 100644
--- a/README
+++ b/README
@@ -39,8 +39,6 @@ IOUtil should not depend on anything
 use a configuration script to amend all thorns' make.code.deps files
 to create the tarballs when the thorns are compiled
 
-use perl instead of C for makeblob and makemetablob
-
 put arrangement name into thorn source name
 use subdirectories for arrangements
 use strings instead of chars for data
@@ -68,6 +66,19 @@ does not have to wait
 
 make max_warn_level and output_info steerable
 
+register with Portal/Announce as information provider
+[Tom/Ian want to make Announce accept a table instead of XMLRPC]
+
+prevent connecting to the wrong simulation, if a simulation is
+outdated, and a new simulation uses the same hostname/port
+combination: the portal can store the job id, and if there is a new
+port id for the same hostname/port combination, deactivate the old
+link.
+
+Rebuild the flesh tarball when the ThornList changes
+
+factor out relaying into its own class
+
 
 
 RSS: add RSS feed
@@ -84,3 +95,10 @@ a simple example is:
     </item>
   </channel>
 </rss>
+
+
+
+Give each value a type.  The type should describe the content, not the
+presentation.  E.g.: "scalar double value, normal range [0..1]", or
+"keyword", or "keyword, possible values are ...", or "integer value,
+value range is [1..10]".