From 8c175e4191cba4134bee93d7f9e44e6ae13d5d5e Mon Sep 17 00:00:00 2001 From: Nico Schottelius Date: Sat, 15 Jan 2011 18:46:44 +0100 Subject: [PATCH] define third provider stage and parts of fourth stage Signed-off-by: Nico Schottelius --- doc/internal/provider-integration | 32 +++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) diff --git a/doc/internal/provider-integration b/doc/internal/provider-integration index 6fe483e9..86d21c88 100644 --- a/doc/internal/provider-integration +++ b/doc/internal/provider-integration @@ -91,3 +91,35 @@ How providers are integrated/run: The idea of this that a provider may expand another provider with functionality, but may need to adjust ("overwrite") settings from the original provider. + + Third stage: + - Cdist calls the "gencode" binary of the providers + for every created object. This binary should create + code to be executed on the target on stdout. + + If the gencode binary fails, it must print diagnostic + messages on stderr and exit non-zero. + + A description of what the generated code may/must/should + do can be found at the end of this document. + + - Cdist merges together the generated code + + Fourth stage: + - The resulting + - Create code to be run on the client. + + +-------------------------------------------------------------------------------- +Scope of code execution on the client + + It should be assumed that the clients are pretty dumb + and thus do not have high level tools like python + installed. + + If a provider requires specific tools to be present + on the target, there must be another provider that + provides this tool and the first provider must create + an object of the specific provider. + +