ABOUT CONTENT
-------------
-Stacks available at './stacks'.
-The launcher uses the configuration given by '.dictionary' which points to a specification list.
-Available different setups by mean files named as '.dictionary__<stack description>'.
+Stacks available at './stacks'. The launcher uses 'dictionary.xml' created ad-hoc by default.
+It is a QoS application dictionary.
-Template for xml messages (message.dtd) and dictionaries (dictionary.dtd) are informative, not
-actually required by process. Located at './DTDs'.
-
-Additional helpers/scripts could be found at './resources' directory.
+Template for xml messages (message.dtd), dictionaries (dictionary.dtd) and services (services.dtd)
+are informative, not actually required by process. Located at './DTDs'.
STARTING THE PROCESS
--------------------
-Start with 'run.sh'. You could manually edit such script adding parameters as '-trace debug' to
-get complete 'launcher.traces'. Execute 'ADL-launcher' without arguments to see a complete
+Start with 'run.sh'. You could manually edit such script adding parameters as '--trace debug' to
+get complete 'launcher.trace'. Execute 'ADML-launcher' without arguments to see a complete
command-line help.
DEPLOYED SCRIPTS
----------------
You could get help about installed resources by mean 'help.sh', which launch a help request to
-the started ADL-launcher process http interface. All the implemented http operations could be
+the started ADML-launcher process http interface. All the implemented http operations could be
launched through a script to make easy use. The http client 'curl' is used by default due to
its presence on common linux distributions.