AppLogic 2.7/2.8 Documentation The latest production release is AppLogic 3.0.30
The text below is used as an included topic in the ADL Reference
Appendix
Future Directions
Per-property quoting style override
The component descriptor syntax allows specifying a single quoting style for a config file, which applies to the entire file. This may not be sufficient to cover for cases when a single file has two or more meta-character quoting methods, depending on context (e.g., in an HTML style, regularly the &...; sequence is used to quote special characters, but in URLs the %xx hex-coded quoting is used.
To provide for cases like this, a per-property override can be defined as an extension of the markup syntax, e.g.:
$$prop value:prop-name(quote-style), ...
More quoting styles
Additional meta-character quoting styles can be added in the future, including:
- user-defined styles (e.g., specified as perl-style replacement commands like: s/&/&/)
- pre-defined styles:
makefile : \<LF> is encoded as \#<LF>, trailing whitespace (<SP><LF>) is encoded as <SP>#<LF>, leading whitespace is not encodeable and is forbidden.
xml : TBD, should be similar to HTML.
Unresolved
"Fixing" the device name for the "external" interface.
The statement found in the text describing the 'interface' sub-entity in a component descriptor says that it is always assigned to the 'eth0' device. This makes the definition of the 'interface external: ...' syntax construct Linux-specific. Also, in Linux it isn't a requirement that an interface of that name exists, either - I, for one, have a setup with a single network interface named 'ath0'.
Global ".failover" group IDs
The failover group ID defined in this specification is global to the application. This may cause conflicts if it is used in instantiable assemblies that are located in a catalog - possibly making unrelated components to "avoid" each other unnecessarily if the same ID was used in two different assemblies without intent to make the components in them belong to the same "failover" group. A safer alternative may be to make the failover group IDs local to an assembly.
-- VladM - 25 May 2006
Copyright © CA 2005-2011. All Rights Reserved.