Bureaucrats, Interface administrators, Administrators (Semantic MediaWiki), Curators (Semantic MediaWiki), Editors (Semantic MediaWiki), Administrators, Widget editors
23,422
edits
MCP-CMS: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 146: | Line 146: | ||
is eponymous from the <a style="background-color:aliceblue;" href=https://meansofproduction.biz/pub/mcpWFL.pdf>original WFL</a> and retains some superficial aesthetics but is radically different in that" | is eponymous from the <a style="background-color:aliceblue;" href=https://meansofproduction.biz/pub/mcpWFL.pdf>original WFL</a> and retains some superficial aesthetics but is radically different in that" | ||
<ul> | <ul> | ||
<li>The Job is not the top level construct. | <li>The Job is not the top level construct. The Job or App is the closest construct to heritage WFL in my WFL but with ops on my MCP rather than the Burroughs/Unisys one and expansion beyond batch ops.<li> | ||
<li>In my WFL, | <li>In my WFL, Namespace, Database, and then App/Job is the scope hierarchy. Namespace and Database are elements of a domain space and may span multiple MCP instances but Jobs are limited to a single MCP.</li> | ||
</ul> | </ul> | ||
In Burroughs systems, WFL didn have as high a profile as IBM JCL, the main punch of the overall system, in an industry installation, would be its system of transactions and these ran from a database which the Burroughs architecture delivered seamlessly without WFL to terminals as a special db stack. Our WFL is the central driver and basis of our MCP/DCP architecture | In Burroughs systems, WFL didn have as high a profile as IBM JCL, the main punch of the overall system, in an industry installation, would be its system of transactions and these ran from a database which the Burroughs architecture delivered seamlessly without WFL to terminals as a special db stack. Our WFL is the central driver and basis of our MCP/DCP architecture | ||
