barant/HTTPServer
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Sync work

Browse Source
This commit is contained in:
Brad Arant 2020-10-21 14:59:21 -07:00
parent bbab38de3a
commit 26fb03572f
7 changed files with 461 additions and 251 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
HTTPServer
View File

Binary file not shown.

106
docs/JETServer Concepts.aux
View File

@ -1,41 +1,83 @@
\relax
\@writefile{toc}{\contentsline {chapter}{\numberline {1}Basic Concepts}{5}}
\@writefile{toc}{\contentsline {chapter}{\numberline {1}Overview}{5}\protected@file@percent }
\@writefile{lof}{\addvspace {10\p@ }}
\@writefile{lot}{\addvspace {10\p@ }}
\@writefile{toc}{\contentsline {section}{\numberline {1.1}Sessions}{5}}
\@writefile{toc}{\contentsline {section}{\numberline {1.2}Views}{5}}
\@writefile{toc}{\contentsline {subsection}{\numberline {1.2.1}View Data Sources}{6}}
\@writefile{toc}{\contentsline {section}{\numberline {1.3}View Components}{6}}
\@writefile{toc}{\contentsline {section}{\numberline {1.4}Forms}{7}}
\@writefile{toc}{\contentsline {section}{\numberline {1.5}Image Library}{7}}
\@writefile{toc}{\contentsline {section}{\numberline {1.6}Work Flow Networks}{7}}
\@writefile{toc}{\contentsline {section}{\numberline {1.7}Requests}{8}}
\@writefile{toc}{\contentsline {section}{\numberline {1.8}Business Entities}{8}}
\@writefile{toc}{\contentsline {section}{\numberline {1.9}Microservice Methods}{8}}
\@writefile{toc}{\contentsline {section}{\numberline {1.10}URIs}{9}}
\@writefile{toc}{\contentsline {section}{\numberline {1.11}Packages}{9}}
\@writefile{toc}{\contentsline {chapter}{\numberline {2}ServerCore Network Platform}{11}}
\@writefile{toc}{\contentsline {chapter}{\numberline {2}Basic Concepts}{7}\protected@file@percent }
\@writefile{lof}{\addvspace {10\p@ }}
\@writefile{lot}{\addvspace {10\p@ }}
\@writefile{toc}{\contentsline {chapter}{\numberline {3}User Interfaces and Tools}{13}}
\@writefile{toc}{\contentsline {chapter}{\numberline {3}Sessions}{9}\protected@file@percent }
\@writefile{lof}{\addvspace {10\p@ }}
\@writefile{lot}{\addvspace {10\p@ }}
\@writefile{toc}{\contentsline {section}{\numberline {3.1}View Layout Editor}{13}}
\@writefile{toc}{\contentsline {section}{\numberline {3.2}Business Entity Editor}{13}}
\@writefile{toc}{\contentsline {section}{\numberline {3.3}Storyboard Editor}{14}}
\@writefile{toc}{\contentsline {chapter}{\numberline {4}JET Tag Reference}{15}}
\@writefile{toc}{\contentsline {chapter}{\numberline {4}Views}{11}\protected@file@percent }
\@writefile{lof}{\addvspace {10\p@ }}
\@writefile{lot}{\addvspace {10\p@ }}
\@writefile{toc}{\contentsline {section}{\numberline {4.1}CALL}{16}}
\@writefile{toc}{\contentsline {section}{\numberline {4.2}COMMENT}{16}}
\@writefile{toc}{\contentsline {section}{\numberline {4.3}DATABASE}{16}}
\@writefile{toc}{\contentsline {section}{\numberline {4.4}EXCLUDE}{16}}
\@writefile{toc}{\contentsline {section}{\numberline {4.5}EXTRACT}{16}}
\@writefile{toc}{\contentsline {section}{\numberline {4.6}FOR}{16}}
\@writefile{toc}{\contentsline {section}{\numberline {4.7}IF.. ELSE}{16}}
\@writefile{toc}{\contentsline {section}{\numberline {4.8}IFNOROW... ELSE}{16}}
\@writefile{toc}{\contentsline {section}{\numberline {4.9}IFROW... ELSE}{16}}
\@writefile{toc}{\contentsline {section}{\numberline {4.10}SYSTEM}{16}}
\@writefile{toc}{\contentsline {section}{\numberline {4.11}TAG}{16}}
\@writefile{toc}{\contentsline {section}{\numberline {4.12}WHILE}{16}}
\@writefile{toc}{\contentsline {section}{\numberline {4.13}WHILEROW}{16}}
\@writefile{toc}{\contentsline {section}{\numberline {4.1}View Components}{12}\protected@file@percent }
\@writefile{toc}{\contentsline {chapter}{\numberline {5}Variables and View Data Sources}{15}\protected@file@percent }
\@writefile{lof}{\addvspace {10\p@ }}
\@writefile{lot}{\addvspace {10\p@ }}
\@writefile{toc}{\contentsline {chapter}{\numberline {6}Forms}{17}\protected@file@percent }
\@writefile{lof}{\addvspace {10\p@ }}
\@writefile{lot}{\addvspace {10\p@ }}
\@writefile{toc}{\contentsline {chapter}{\numberline {7}Image Library}{19}\protected@file@percent }
\@writefile{lof}{\addvspace {10\p@ }}
\@writefile{lot}{\addvspace {10\p@ }}
\@writefile{toc}{\contentsline {chapter}{\numberline {8}Work Flow Networks}{21}\protected@file@percent }
\@writefile{lof}{\addvspace {10\p@ }}
\@writefile{lot}{\addvspace {10\p@ }}
\@writefile{toc}{\contentsline {section}{\numberline {8.1}Work Flow Units}{21}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{\numberline {8.2}Work Flow Queues}{22}\protected@file@percent }
\@writefile{toc}{\contentsline {subsection}{\numberline {8.2.1}Action Queues}{22}\protected@file@percent }
\@writefile{toc}{\contentsline {subsection}{\numberline {8.2.2}External Queues}{22}\protected@file@percent }
\@writefile{toc}{\contentsline {subsection}{\numberline {8.2.3}Decision Queues}{22}\protected@file@percent }
\@writefile{toc}{\contentsline {subsection}{\numberline {8.2.4}Wait Queues}{22}\protected@file@percent }
\@writefile{toc}{\contentsline {subsection}{\numberline {8.2.5}Process Queues}{22}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{\numberline {8.3}Permanent Work Flow Procedures}{22}\protected@file@percent }
\@writefile{toc}{\contentsline {subsection}{\numberline {8.3.1}Administration Work Flow Procedures}{22}\protected@file@percent }
\@writefile{toc}{\contentsline {subsection}{\numberline {8.3.2}Initial Transaction Work Flow Procedure}{23}\protected@file@percent }
\@writefile{toc}{\contentsline {chapter}{\numberline {9}Requests}{25}\protected@file@percent }
\@writefile{lof}{\addvspace {10\p@ }}
\@writefile{lot}{\addvspace {10\p@ }}
\@writefile{toc}{\contentsline {section}{\numberline {9.1}Microservice Methods}{25}\protected@file@percent }
\@writefile{toc}{\contentsline {chapter}{\numberline {10}Defining URL, Links and Deep Links}{27}\protected@file@percent }
\@writefile{lof}{\addvspace {10\p@ }}
\@writefile{lot}{\addvspace {10\p@ }}
\@writefile{toc}{\contentsline {chapter}{\numberline {11}Business Entities}{29}\protected@file@percent }
\@writefile{lof}{\addvspace {10\p@ }}
\@writefile{lot}{\addvspace {10\p@ }}
\@writefile{toc}{\contentsline {chapter}{\numberline {12}Libraries}{31}\protected@file@percent }
\@writefile{lof}{\addvspace {10\p@ }}
\@writefile{lot}{\addvspace {10\p@ }}
\@writefile{toc}{\contentsline {chapter}{\numberline {13}Server Directory Structure}{33}\protected@file@percent }
\@writefile{lof}{\addvspace {10\p@ }}
\@writefile{lot}{\addvspace {10\p@ }}
\@writefile{toc}{\contentsline {chapter}{\numberline {14}ServerCore Network Platform}{35}\protected@file@percent }
\@writefile{lof}{\addvspace {10\p@ }}
\@writefile{lot}{\addvspace {10\p@ }}
\@writefile{toc}{\contentsline {section}{\numberline {14.1}Transaction Life Cycle}{35}\protected@file@percent }
\@writefile{toc}{\contentsline {chapter}{\numberline {15}User Interfaces and Tools}{37}\protected@file@percent }
\@writefile{lof}{\addvspace {10\p@ }}
\@writefile{lot}{\addvspace {10\p@ }}
\@writefile{toc}{\contentsline {section}{\numberline {15.1}View Layout Editor}{37}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{\numberline {15.2}Business Entity Editor}{37}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{\numberline {15.3}Storyboard Editor}{38}\protected@file@percent }
\@writefile{toc}{\contentsline {chapter}{\numberline {16}Views and User Interface Components}{39}\protected@file@percent }
\@writefile{lof}{\addvspace {10\p@ }}
\@writefile{lot}{\addvspace {10\p@ }}
\@writefile{toc}{\contentsline {section}{\numberline {16.1}View Hierarchy}{39}\protected@file@percent }
\@writefile{toc}{\contentsline {chapter}{\numberline {17}JET Tag Reference}{41}\protected@file@percent }
\@writefile{lof}{\addvspace {10\p@ }}
\@writefile{lot}{\addvspace {10\p@ }}
\@writefile{toc}{\contentsline {section}{\numberline {17.1}CALL}{42}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{\numberline {17.2}COMMENT}{42}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{\numberline {17.3}DATABASE}{42}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{\numberline {17.4}EXCLUDE}{42}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{\numberline {17.5}EXTRACT}{42}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{\numberline {17.6}FOR}{42}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{\numberline {17.7}IF.. ELSE}{42}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{\numberline {17.8}IFNOROW... ELSE}{42}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{\numberline {17.9}IFROW... ELSE}{42}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{\numberline {17.10}INCLUDE}{42}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{\numberline {17.11}SYSTEM}{42}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{\numberline {17.12}TAG}{42}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{\numberline {17.13}WHILE}{42}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{\numberline {17.14}WHILEROW}{42}\protected@file@percent }

333
docs/JETServer Concepts.log
View File

@ -1,31 +1,38 @@
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian) (preloaded format=pdflatex 2019.5.23) 23 AUG 2019 11:48
This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Debian) (preloaded format=pdflatex 2020.4.16) 9 SEP 2020 19:05
entering extended mode
restricted \write18 enabled.
%&-line parsing enabled.
**"JETServer Concepts.tex"
(./JETServer Concepts.tex
LaTeX2e <2017-04-15>
Babel <3.18> and hyphenation patterns for 5 language(s) loaded.
LaTeX2e <2020-02-02> patch level 2
L3 programming layer <2020-02-14>
(/usr/share/texlive/texmf-dist/tex/latex/base/book.cls
Document Class: book 2014/09/29 v1.4h Standard LaTeX document class
Document Class: book 2019/12/20 v1.4l Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/bk10.clo
File: bk10.clo 2014/09/29 v1.4h Standard LaTeX file (size option)
File: bk10.clo 2019/12/20 v1.4l Standard LaTeX file (size option)
)
\c@part=\count79
\c@chapter=\count80
\c@section=\count81
\c@subsection=\count82
\c@subsubsection=\count83
\c@paragraph=\count84
\c@subparagraph=\count85
\c@figure=\count86
\c@table=\count87
\abovecaptionskip=\skip41
\belowcaptionskip=\skip42
\bibindent=\dimen102
\c@part=\count167
\c@chapter=\count168
\c@section=\count169
\c@subsection=\count170
\c@subsubsection=\count171
\c@paragraph=\count172
\c@subparagraph=\count173
\c@figure=\count174
\c@table=\count175
\abovecaptionskip=\skip47
\belowcaptionskip=\skip48
\bibindent=\dimen134
)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
Package: graphicx 2019/11/30 v1.2a Enhanced LaTeX Graphics (DPC,SPQR)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty
Package: keyval 2014/10/28 v1.15 key=value parser (DPC)
\KV@toks@=\toks14
)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
Package: graphics 2017/06/25 v1.2c Standard LaTeX Graphics (DPC,SPQR)
Package: graphics 2019/11/30 v1.4a Standard LaTeX Graphics (DPC,SPQR)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty
Package: trig 2016/01/03 v1.10 sin cos tan (DPC)
@ -33,95 +40,62 @@ Package: trig 2016/01/03 v1.10 sin cos tan (DPC)
(/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg
File: graphics.cfg 2016/06/04 v1.11 sample graphics configuration
)
Package graphics Info: Driver file: pdftex.def on input line 99.
Package graphics Info: Driver file: pdftex.def on input line 105.
(/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def
File: pdftex.def 2018/01/08 v1.0l Graphics/color driver for pdftex
))
\Gin@req@height=\dimen135
\Gin@req@width=\dimen136
)
(/usr/share/texlive/texmf-dist/tex/latex/wrapfig/wrapfig.sty
\wrapoverhang=\dimen137
\WF@size=\dimen138
\c@WF@wrappedlines=\count176
\WF@box=\box45
\WF@everypar=\toks15
Package: wrapfig 2003/01/31 v 3.6
)
(/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-pdfmode.def
File: l3backend-pdfmode.def 2020-02-03 L3 backend support: PDF mode
\l__kernel_color_stack_int=\count177
\l__pdf_internal_box=\box46
)
(./JETServer Concepts.aux)
\openout1 = `"JETServer Concepts.aux"'.
LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 4.
LaTeX Font Info: ... okay on input line 4.
LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 4.
LaTeX Font Info: ... okay on input line 4.
LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 4.
LaTeX Font Info: ... okay on input line 4.
LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 4.
LaTeX Font Info: ... okay on input line 4.
LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 4.
LaTeX Font Info: ... okay on input line 4.
LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 4.
LaTeX Font Info: ... okay on input line 4.
LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 5.
LaTeX Font Info: ... okay on input line 5.
LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 5.
LaTeX Font Info: ... okay on input line 5.
LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 5.
LaTeX Font Info: ... okay on input line 5.
LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 5.
LaTeX Font Info: ... okay on input line 5.
LaTeX Font Info: Checking defaults for TS1/cmr/m/n on input line 5.
LaTeX Font Info: ... okay on input line 5.
LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 5.
LaTeX Font Info: ... okay on input line 5.
LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 5.
LaTeX Font Info: ... okay on input line 5.
(/usr/share/texlive/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
[Loading MPS to PDF converter (version 2006.09.02).]
\scratchcounter=\count88
\scratchdimen=\dimen103
\scratchbox=\box26
\nofMPsegments=\count89
\nofMParguments=\count90
\everyMPshowfont=\toks14
\MPscratchCnt=\count91
\MPscratchDim=\dimen104
\MPnumerator=\count92
\makeMPintoPDFobject=\count93
\everyMPtoPDFconversion=\toks15
) (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/epstopdf-base.sty
Package: epstopdf-base 2016/05/15 v2.6 Base part for package epstopdf
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/infwarerr.sty
Package: infwarerr 2016/05/16 v1.4 Providing info/warning/error messages (HO)
)
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/grfext.sty
Package: grfext 2016/05/16 v1.2 Manage graphics extensions (HO)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/kvdefinekeys.sty
Package: kvdefinekeys 2016/05/16 v1.4 Define keys (HO)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ltxcmds.sty
Package: ltxcmds 2016/05/16 v1.23 LaTeX kernel commands for general use (HO)
)))
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty
Package: kvoptions 2016/05/16 v3.12 Key value format for package options (HO)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty
Package: keyval 2014/10/28 v1.15 key=value parser (DPC)
\KV@toks@=\toks16
)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/kvsetkeys.sty
Package: kvsetkeys 2016/05/16 v1.17 Key value parser (HO)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/etexcmds.sty
Package: etexcmds 2016/05/16 v1.6 Avoid name clashes with e-TeX commands (HO)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty
Package: ifluatex 2016/05/16 v1.4 Provides the ifluatex switch (HO)
Package ifluatex Info: LuaTeX not detected.
)
Package etexcmds Info: Could not find \expanded.
(etexcmds) That can mean that you are not using pdfTeX 1.50 or
(etexcmds) that some package has redefined \expanded.
(etexcmds) In the latter case, load this package earlier.
)))
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/pdftexcmds.sty
Package: pdftexcmds 2018/01/21 v0.26 Utility functions of pdfTeX for LuaTeX (HO
)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty
Package: ifpdf 2017/03/15 v3.2 Provides the ifpdf switch
)
Package pdftexcmds Info: LuaTeX not detected.
Package pdftexcmds Info: \pdf@primitive is available.
Package pdftexcmds Info: \pdf@ifprimitive is available.
Package pdftexcmds Info: \pdfdraftmode found.
)
\scratchcounter=\count178
\scratchdimen=\dimen139
\scratchbox=\box47
\nofMPsegments=\count179
\nofMParguments=\count180
\everyMPshowfont=\toks16
\MPscratchCnt=\count181
\MPscratchDim=\dimen140
\MPnumerator=\count182
\makeMPintoPDFobject=\count183
\everyMPtoPDFconversion=\toks17
) (/usr/share/texlive/texmf-dist/tex/latex/epstopdf-pkg/epstopdf-base.sty
Package: epstopdf-base 2020-01-24 v2.11 Base part for package epstopdf
Package epstopdf-base Info: Redefining graphics rule for `.eps' on input line 4
38.
Package grfext Info: Graphics extension search list:
(grfext) [.pdf,.png,.jpg,.mps,.jpeg,.jbig2,.jb2,.PDF,.PNG,.JPG,.JPE
G,.JBIG2,.JB2,.eps]
(grfext) \AppendGraphicsExtensions on input line 456.
85.
(/usr/share/texlive/texmf-dist/tex/latex/latexconfig/epstopdf-sys.cfg
File: epstopdf-sys.cfg 2010/07/13 v1.3 Configuration of (r)epstopdf for TeX Liv
@ -135,30 +109,42 @@ e
]
(./JETServer Concepts.toc
LaTeX Font Info: External font `cmex10' loaded for size
(Font) <7> on input line 2.
(Font) <7> on input line 5.
LaTeX Font Info: External font `cmex10' loaded for size
(Font) <5> on input line 2.
)
(Font) <5> on input line 5.
[3])
\tf@toc=\write3
\openout3 = `"JETServer Concepts.toc"'.
[3] [4]
[4]
Chapter 1.
Overfull \hbox (7.61179pt too wide) in paragraph at lines 33--34
\OT1/cmr/m/n/10 for ex-ten-si-bil-ity of ca-pa-bil-i-ties in-clud-ing frame-wor
ks, work flows, styles, databases,
[]
[5
] [6] [7] [8] [9] [10
] [6
]
Chapter 2.
<images/classcore_1_1_socket__inherit__graph.png, id=39, 715.67375pt x 412.5412
4pt>
File: images/classcore_1_1_socket__inherit__graph.png Graphic file (type png)
<use images/classcore_1_1_socket__inherit__graph.png>
Package pdftex.def Info: images/classcore_1_1_socket__inherit__graph.png used
on input line 169.
(pdftex.def) Requested size: 715.672pt x 412.54024pt.
[7] [8
Overfull \hbox (385.672pt too wide) in paragraph at lines 169--170
]
Chapter 3.
[9] [10
]
Chapter 4.
<images/graphical_concept.png, id=40, 770.88pt x 446.66875pt>
File: images/graphical_concept.png Graphic file (type png)
<use images/graphical_concept.png>
Package pdftex.def Info: images/graphical_concept.png used on input line 67.
(pdftex.def) Requested size: 345.0pt x 199.90176pt.
Overfull \hbox (15.0pt too wide) in paragraph at lines 67--68
[][]
[]
@ -166,37 +152,112 @@ Overfull \hbox (385.672pt too wide) in paragraph at lines 169--170
Underfull \vbox (badness 10000) has occurred while \output is active []
[11]
[12 <./images/classcore_1_1_socket__inherit__graph.png>]
Chapter 3.
[13
<images/view_component_structure.png, id=45, 442.65375pt x 241.90375pt>
File: images/view_component_structure.png Graphic file (type png)
<use images/view_component_structure.png>
Package pdftex.def Info: images/view_component_structure.png used on input lin
e 81.
(pdftex.def) Requested size: 345.0pt x 188.54758pt.
Overfull \hbox (15.0pt too wide) in paragraph at lines 81--82
[][]
[]
] [14]
Chapter 4.
Underfull \vbox (badness 10000) has occurred while \output is active []
[15
[12 <./images/graphical_concept.png>] [13 <./images/view_component_structure.p
ng>]
[14
]
[16] (./JETServer Concepts.aux) )
Here is how much of TeX's memory you used:
1397 strings out of 494880
20127 string characters out of 6179601
74925 words of memory out of 5000000
4732 multiletter control sequences out of 15000+600000
7069 words of font info for 25 fonts, out of 8000000 for 9000
36 hyphenation exceptions out of 8191
41i,5n,25p,479b,141s stack positions out of 5000i,500n,10000p,200000b,80000s
</usr/share/texlive/texmf-dist/fonts/type1/pub
lic/amsfonts/cm/cmbx10.pfb></usr/share/texlive/texmf-dist/fonts/type1/public/am
sfonts/cm/cmbx12.pfb></usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts
/cm/cmr10.pfb></usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cms
l10.pfb></usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmti10.pf
b>
Output written on "JETServer Concepts.pdf" (16 pages, 122185 bytes).
PDF statistics:
79 PDF objects out of 1000 (max. 8388607)
53 compressed objects within 1 object stream
0 named destinations out of 1000 (max. 500000)
6 words of extra memory for PDF output out of 10000 (max. 10000000)
Chapter 5.
[15] [16
]
Chapter 6.
[17] [18
]
Chapter 7.
[19] [20
]
Chapter 8.
[21] [22] [23] [24
]
Chapter 9.
[25] [26]
Chapter 10.
[27
] [28
]
Chapter 11.
[29] [30
]
Chapter 12.
[31] [32
]
Chapter 13.
[33] [34
]
Chapter 14.
<images/classcore_1_1_socket__inherit__graph.png, id=121, 715.67375pt x 412.541
24pt>
File: images/classcore_1_1_socket__inherit__graph.png Graphic file (type png)
<use images/classcore_1_1_socket__inherit__graph.png>
Package pdftex.def Info: images/classcore_1_1_socket__inherit__graph.png used
on input line 238.
(pdftex.def) Requested size: 284.52756pt x 164.01268pt.
[35 <./images/classcore_1_1_socket__inherit__graph.png>]
<images/transaction_lifecycle.png, id=126, 369.38pt x 894.34125pt>
File: images/transaction_lifecycle.png Graphic file (type png)
<use images/transaction_lifecycle.png>
Package pdftex.def Info: images/transaction_lifecycle.png used on input line 2
47.
(pdftex.def) Requested size: 86.25pt x 208.81921pt.
[36 <./images/transaction_lifecycle.png>]
Chapter 15.
[37
] [38]
Chapter 16.
[39
] [40
]
Chapter 17.
Underfull \vbox (badness 10000) has occurred while \output is active []
[41]
[42] (./JETServer Concepts.aux) )
Here is how much of TeX's memory you used:
1269 strings out of 483140
19018 string characters out of 5965151
248227 words of memory out of 5000000
16321 multiletter control sequences out of 15000+600000
536102 words of font info for 36 fonts, out of 8000000 for 9000
36 hyphenation exceptions out of 8191
30i,5n,25p,549b,168s stack positions out of 5000i,500n,10000p,200000b,80000s
</home/bradarant/.texlive2019/texmf-var/fonts
/pk/ljfour/jknappen/ec/tcrm1000.600pk></usr/share/texlive/texmf-dist/fonts/type
1/public/amsfonts/cm/cmbx10.pfb></usr/share/texlive/texmf-dist/fonts/type1/publ
ic/amsfonts/cm/cmbx12.pfb></usr/share/texlive/texmf-dist/fonts/type1/public/ams
fonts/cm/cmr10.pfb></usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/c
m/cmsl10.pfb></usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmti
10.pfb>
Output written on "JETServer Concepts.pdf" (42 pages, 222200 bytes).
PDF statistics:
175 PDF objects out of 1000 (max. 8388607)
115 compressed objects within 2 object streams
0 named destinations out of 1000 (max. 500000)
21 words of extra memory for PDF output out of 10000 (max. 10000000)

BIN
docs/JETServer Concepts.pdf
View File

Binary file not shown.

BIN
docs/JETServer Concepts.synctex.gz
View File

Binary file not shown.

193
docs/JETServer Concepts.tex
View File

@ -1,5 +1,6 @@
\documentclass[10pt]{book}
\usepackage{graphics}
\usepackage{graphicx}
\usepackage{wrapfig}
\graphicspath{/home/barant/HTTPServer/images}
\begin{document}
@ -25,11 +26,17 @@
\tableofcontents
\chapter{Overview}
JETServer provides a complete environment for developing very powerful and feature rich web content using standard browsers. It is intended to compete and replace the aging WordPress environments that comprise a huge number of websites. JETServer is designed with high performance in mind utilizing a combination of HTML5, CSS3 and Javascript.
JETServer is designed to support a plugin environment, known as libraries, for extensibility of capabilities including frameworks, work flows, styles, databases, etc.
\chapter{Basic Concepts}
In this chapter we will cover the components that make up the JETServer environment.
\section{Sessions}
\chapter{Sessions}
Sessions provide a congruent and flowing state management for a connected browser. The states of various elements are stored and kept as a part of the session information so a browser refresh will not disrupt the work flow intended by the application logic.
@ -41,7 +48,7 @@ The session mechanism will attempt to maintain a \emph{state} of the interaction
As requests are placed the request URI is saved to the http session. If needed, perhaps because of a refresh, the page state can be recreated from the saved URI list. Other data and state information can be stored to the session as well.
\section{Views}
\chapter{Views}
Views are document sections that can be placed into the page. Views can be static or can contain dynamic data elements. Views can also contain other views in a nested fashion.
@ -57,58 +64,112 @@ Views that have URIs attached to them are considered document level views and wi
TABLE elements can also be specified in a view.
\includegraphics[width=\textwidth]{images/graphical_concept.png}
Javascript code can be attached to components within the view or to the view itself. Custom components can be built that plug into the layout tool environment and can be designed into the application environment with prebuilt behaviors. Complex display control can be constructed using these tools.
Views can optionally contain a \emph{subview} element that can be used to provide a placeholder for subsequent view requests. When these are provided inside a view the view will act as a template that can encapsulate the subview.
\subsection{View Data Sources}
Data is available to be displayed and represented that is only available when the views are rendered. Sources of this data are as follows:
\begin{enumerate}
\item Set variable performed in the view code or from a previously run process in the same transaction to name a piece of data for later use.
\item CGI data received in the request as form-data is available to the request handler. Use the [:variable-name] syntax to ensure that CGI data is the source of the data.
\item Session variables provide access to persistent storage that survives for the duration of the session.
\item A data result table that was retrieved from an mySQL buffer.
\end{enumerate}
Standard variable syntax of just using variable-name will perform a search for a variable regardless of its type but prioritized by the following order:
Views can optionally contain a \emph{request} element that can be used to provide a placeholder for subsequent view requests. When these are provided inside a view the view will act as a template that can encapsulate the subview. Request viewholders are usually tied to a URL component so that as a session presentation is being created it may use conponents in the URL to determine the content to display. Hidden requests are requests that use private session data to determine the content to display.
\section{View Components}
View Components are packaged HTML5, CSS and Javascript elements that are defined to be used together as a component within another view (usually and layout view).
Views may utilize HTML constructs to assemble part of its implementation. The use of <IMG>, <FORM>, <INPUT>, <TEXTAREA> and a significant list of other items can be contained within a view.
The view can contain javascript that is used to interact with these components.
\section{Forms}
\includegraphics[width=\textwidth]{images/view_component_structure.png}
\chapter{Variables and View Data Sources}
Data is available to be displayed and represented that is only available when the views are rendered. Sources of this data are as follows:
Standard variable syntax of just using variable-name will perform a search for a variable regardless of its type but prioritized by the following order:
\begin{enumerate}
\item a variable set using the <set> tag. These variable persist for the life of the current transaction only.
\item data retrieved from a POST within a request and are defined as visible TEXT, BUTTON and TEXTAREA and hidden <INPUT> fields
\item a session variable set using the <setsession> tag. These varables persist fo the entire session.
\item an environment variable from the JETServer runtime environment. These variables are set when the server is started and do not change for the life of the server runtime.
\item a mySQL server result table created in the last SELECT statement. The persistence of these variables is only for the life of the open data path or until another operation is performed within the same access path to the database. Each open data path can return results without qualification and the order of the database specification will determine search order. When databases are opened for use in content an associated session name that is used to differentiate multiple open access paths simultaneously.
\end{enumerate}
\chapter{Forms}
Using the INPUT tag within a FORM tag allows the submission of the related form data to the server to be processed as a POST request. A BUTTON can perform this activity and request a microservices method and pass the form data along as a parameter to the request.
BUTTONs are attached to server side microservice methods.
\section{Image Library}
\chapter{Image Library}
Significant content can be provided in the form of images and are used as part of a design. The image library is not intended to be a photo cataloguing function but is designed to provide image support to the view elements such as logos. Catalogues can be accomplished through other means and usually tie into an external database system of some kind.
Significant content can be provided in the form of images and are used as part of a design. The image library is not intended to be a photo cataloguing function but is designed to provide image support to the view elements such as logos. The View Layout Editor is used to access the image library for inclusion into a view. Images can be placed in views and resized or rotated.
\section{Work Flow Networks}
Imagemagick is used internally to create a scaled and rotated version of the image for network optimization resulting in improved performance. These scaled and rotated images exist in the permanent cache and are always checked first when rendering images to the browser.
Images create a corresponding IMG tag that the browser consumes to request the selected images.
\chapter{Work Flow Networks}
JETServer is a complete work flow engine capable of delivering extremely sophisticated work flow requirements on various business data sets. Performing various activities on business entities creates needs for scheduling follow-ups and other automatic processed based upon very long time delays or other triggers that cause the need for more immediate action.
Work flow processes are initiated on a particular business entity and stick to the entity throughout the definition of the work flow process. At any one time there could be many work flow tags running on any one piece of data at a time.
Work flow processes are initiated on a particular business entity and stick to the entity throughout the definition of the work flow process. At any one time there could be many work flow tags running on any one piece of data at a time. As well, work flow processes may initiate another work fow procedure on the same business entity or a different one that is related.
Work flow processes can be initiated on a button press using the initiateWorkFlow API call. They are attached to a business entity and they may trigger other work flow processe on other entities related to various activities. Work flow process are very powerful trackers where things otherwise may slip through the cracks. Watch dog work flows can be ceated to ensure all activities are being handled and performed to avoid stale data situations.
Work Flow Networks are developed using a graphical flow chart style workbench that allows the business process analyst to snap together activities that are to be performed by automated process and/or user interaction. Work Queue objects are available to design work lists for users to interact with items requiring intervention. Users can review various work queues and perform the requested activities to complete the work flow requirements.
\section{Requests}
\section {Work Flow Units}
Work flow units are created when a work flow process is initiated on a business entity. A work flow unit (WFU) contains the business entity and a work flow identifier and a queue identifier. As the WFU moves through the work flow patterns the queue identifier is updated to represent its 'state'.
\section{Work Flow Queues}
As work flow units move through the process they move from queue to queue. The various queue types perform perscribed operations on the work flow unit moving through the procedure. The queue types are as follows:
\begin{enumerate}
\item Action Queues - as work flows are constructed they are placed into a container called an action queue.
\item External Queues - provides a visual access point to the data entity referenced by the WFU. External queues reference views that are sent to the client as output to the work flow and the work flow is suspended until an appropriate POST operation is sent to the server in response to the work flow requirements.
\item Decision Queues - provides a method to perform tests upon the reference business entity and branch the work flow based upon the test outcome.
\item Wait Queues - these queues provide a place for the WFU to wait indefinetly or for perscribed periods of time before the WFU is passed to the next queue. The wait queue can return a list of WFUs that are currently contained so that work lists and other lists can be analyzed and worked with externally to satisfy work flow requirements.
\item Process Queues - these queues can perform a system call to perform advanced operations and can control the flow of the WFU based upon the operation's outcome.
\end{enumerate}
\subsection{Action Queues}
\subsection{External Queues}
\subsection{Decision Queues}
\subsection{Wait Queues}
\subsection{Process Queues}
\section{Permanent Work Flow Procedures}
\subsection{Administration Work Flow Procedures}
Special procedures designed to maintain the basic operations of the website are contained in an internal area compiled with the executable so they remain unchangeable without version upgrades.
Upon initial installation and startup of the server a welcome page is presented with a button the setup the administrative access options. Once this is accomplished then the administractive mode of the server is entered and the user is entered into the administration menu functions for the server.
\subsection{Initial Transaction Work Flow Procedure}
Initial work flow begins with the init work flow procedure aptly named 'init' in the root folder of the 'worflow' directory. The init procedure defines the nature and lifespan of the transaction received from the browser.
If the init procedure is absent in the folder then a default procedure is used. The default procedure offers the full functionality of the JETServer. It will receive the user request and do the session lookups and perform the view hierarchy operations.
Libraries will be searched in the order defined by library list contained withing the libraries subfolder. First match will proide that resource to the rendering of the current page cycle.
\chapter{Requests}
Requests are view 'placeholders' that can be used to make a request to the server and have the response be displayed in the viewport of the request. Requests are the fundamental building block to creating extended content pages.
@ -122,7 +183,25 @@ A request response will contain HTML document data that will be replaced as the
The document content of the response may contain a script tag which contains javascript that executes immediately after the HTML is attached to the document.
\section{Business Entities}
\section{Microservice Methods}
JETServer uses a microservices style architecture and provides access to backend services through an API set that is designed to interact with the various view components of the application. In essence the work flow engine will create microservice functions available only to the session providing a highly secure API system as all other sessions or attempts at accessing functions will be rejected if the work flow does not permit the operation.
Microservice methods are oriented around the business entity structure and are used to provide information query handling as well as the add, update and delete functionality of new business entity instances.
Microservice methods can also be used to provide lists of objects that can be further used in modifying or removing instances.
Applications can be designed that employ various business logic entities. Views that define forms for adding new customers or information on books or some other data entity can be specified and attached to the business entity. Common lists of objects that have filters applied can be retrieved and views selected for presentation of the data.
\chapter{Defining URL, Links and Deep Links}
Because the session manages the states for presentation the contents of the page are directly linked to a URL which can be used to recreate the contents in the event of an interruption. Also, a link is an entry point to the website that contains a complete structure to recreate the contents. Pages will usually consist of various viewpoints which make requests upon the server to fulfill the content requirements specified by a URL.
A URI provides an external access string to be mapped to a site view. When a browser submits a GET request to a URI that is mapped to the server then it will return the resulting site marker forcing the session to check its current state and send the appropriate information.
The URI may be specified as \emph{complete} or \emph{partial}. Partial URI specification will match the pattern check but will also pass additional parameters not specified into the view so that it may parse the content and provide the appropriate display result.
\chapter{Business Entities}
Business entities provide the framework in which to hang all thiese views and logic. Business entities allow for the description of account, customers, products, inventories and any other associated data elements that may be used in business logic consideration.
@ -130,27 +209,13 @@ Instances of business entities are considered entity objects or entity instances
Views are associated with a business entity combined with a microservice method to create functionality.
\section{Microservice Methods}
\chapter{Libraries}
JETServer uses a microservices style architecture and provides access to backend services through an API set that is designed to interact with the various view components of the application.
Libraries provide extensibility to the JETServer environment by allowing custom tools, applications, themes, templates, entities and components to be added to the server and utilized in the presentation. Installed packages are provided a root namespace and all related content must be contained and extended by the 'library' root path namespace.
Microservice methods are oriented around the business entity structure and are used to provide information query handling as well as the add, update and delete functionality of new business entity instances.
The 'libraries' subfolder must contain a library list file that contains a simple list of the order in which the libraries contained herein are to be search for resolving resouce names. Updates to the library list file will immediately be applied to the next transaction. Transactions still in process will not be changed.
Microservice methods can also be used to provide lists of objects that can be further used in modifying or removing instances.
Applications can be designed that employee various business logic entities. Views that define forms for adding new customers or information on books or some other data entity can be specified and attached to the business entity. Common lists of objects that have filters applied can be retrieved and views selected for presentation of the data.
\section{URIs}
A URI provides an external access string to be mapped to a site view. When a browser submits a GET request to a URI that is mapped to the server then it will return the resulting site marker forcing the session to check its current state and send the appropriate information.
The URI may be specified as \emph{complete} or \emph{partial}. Partial URI specification will match the pattern check but will also pass additional parameters not specified into the view so that it may parse the content and provide the appropriate display result.
\section{Packages}
Packages provide extensibility to the JETServer environment by allowing custom tools, applications, themes, templates, entities and components to be added to the server and utilized in the presentation. Installed packages are provided a root namespace and all related content must be contained and extended by this root path namespace.
Packages can contain many things including full application request flows that can be integrated into other work flows or used as is.
Libraries can contain many things including full application request flows that can be integrated into other work flows or used as is.
Local code is setup automatically in a default package named 'local'. The local package is always searched first when resolving names to finding objects.
@ -160,13 +225,31 @@ You can create an empty package and give it a namespace and write custom items i
It is intended to provide a JETStore for the user to browse for registered packages of all kinds from themes to full application work flows. It is hopeful that someday there will be a rich environment for providing tools and applications for the JETServer system.
\chapter{Server Directory Structure}
JETServer depends upon a hierarchical file system to provide the system functions. Libraries are stored as copies of the basic hierarchical structure that act as a qualified namespace.
\chapter{ServerCore Network Platform}
JETServer is utilizing the ServerCore library to implement the TCP networking requirements. Using the Linux operating system and the epoll system architecture JETServer delivers high performance networking with extreme control.
Written in C++ JETServer is designed for performance at all levels of the technical implementation. Using the core namespace along with the http namespace to create the basic core functionality JETServer provides a framework in which to create complete work flow patterns required to build complex applications.
\includegraphics{images/classcore_1_1_socket__inherit__graph.png}
\includegraphics[width=10cm]{images/classcore_1_1_socket__inherit__graph.png}
\section{Transaction Life Cycle}
JETServer is a complete HTTP request server in full compliance with the latest standards. Internally it can also mesh itself into a network of JETServers and will automatically adjust and load balance traffic requests coming through the server.
Being an HTTP request server JETServer must conform to CGI specifications that are used to interact with the browser.
\begin{wrapfigure}{R}{0.3\textwidth}
\includegraphics[width=0.25\textwidth]{images/transaction_lifecycle.png}
\end{wrapfigure}
For e ach received request JETServer will generate appropriate code sections and output them through the CGI gateway process for rendering by the browser.
Form Field Data Cache provides access to the form variables received in the request.When the CGI data is parsed from the request it is placed in this cache for access by processes that may require it during the transaction life cycle.
\chapter{User Interfaces and Tools}
@ -195,6 +278,13 @@ The design approach provides the ability to layout \emph{request} objects and as
Various views can be layed out in the storyboard. Storyboards are based around the request object as each request object will perform a request activity which may result in a chain of further request events.
\chapter{Views and User Interface Components}
JETServer enables a simple architecture for presenting and controlling the presentation. Interaction with the user is accomplished with various standard components that interact with workflows generated from the events which the component may produce.
\section{View Hierarchy}
Views are managed as a hierarchy of nested references to view components defined in the 'view' subfolder. The determination of which view to deliver to the requester is made through the parsing of the requested URL being passed from the requester. The tree hierarchy is maintained as views are added, changed and removed from visibility through event processing. If a refresh (F5) is performed on the URL the engine will render the identical page before the refresh was requested.
\chapter{JET Tag Reference}
JET tags can be used within views as well as microservice methods to build business logic.
@ -208,6 +298,7 @@ JET tags can be used within views as well as microservice methods to build busin
\section{IF.. ELSE}
\section{IFNOROW... ELSE}
\section{IFROW... ELSE}
\section{INCLUDE}
\section{SYSTEM}
\section{TAG}
\section{WHILE}

80
docs/JETServer Concepts.toc
View File

@ -1,32 +1,48 @@
\contentsline {chapter}{\numberline {1}Basic Concepts}{5}
\contentsline {section}{\numberline {1.1}Sessions}{5}
\contentsline {section}{\numberline {1.2}Views}{5}
\contentsline {subsection}{\numberline {1.2.1}View Data Sources}{6}
\contentsline {section}{\numberline {1.3}View Components}{6}
\contentsline {section}{\numberline {1.4}Forms}{7}
\contentsline {section}{\numberline {1.5}Image Library}{7}
\contentsline {section}{\numberline {1.6}Work Flow Networks}{7}
\contentsline {section}{\numberline {1.7}Requests}{8}
\contentsline {section}{\numberline {1.8}Business Entities}{8}
\contentsline {section}{\numberline {1.9}Microservice Methods}{8}
\contentsline {section}{\numberline {1.10}URIs}{9}
\contentsline {section}{\numberline {1.11}Packages}{9}
\contentsline {chapter}{\numberline {2}ServerCore Network Platform}{11}
\contentsline {chapter}{\numberline {3}User Interfaces and Tools}{13}
\contentsline {section}{\numberline {3.1}View Layout Editor}{13}
\contentsline {section}{\numberline {3.2}Business Entity Editor}{13}
\contentsline {section}{\numberline {3.3}Storyboard Editor}{14}
\contentsline {chapter}{\numberline {4}JET Tag Reference}{15}
\contentsline {section}{\numberline {4.1}CALL}{16}
\contentsline {section}{\numberline {4.2}COMMENT}{16}
\contentsline {section}{\numberline {4.3}DATABASE}{16}
\contentsline {section}{\numberline {4.4}EXCLUDE}{16}
\contentsline {section}{\numberline {4.5}EXTRACT}{16}
\contentsline {section}{\numberline {4.6}FOR}{16}
\contentsline {section}{\numberline {4.7}IF.. ELSE}{16}
\contentsline {section}{\numberline {4.8}IFNOROW... ELSE}{16}
\contentsline {section}{\numberline {4.9}IFROW... ELSE}{16}
\contentsline {section}{\numberline {4.10}SYSTEM}{16}
\contentsline {section}{\numberline {4.11}TAG}{16}
\contentsline {section}{\numberline {4.12}WHILE}{16}
\contentsline {section}{\numberline {4.13}WHILEROW}{16}
\contentsline {chapter}{\numberline {1}Overview}{5}%
\contentsline {chapter}{\numberline {2}Basic Concepts}{7}%
\contentsline {chapter}{\numberline {3}Sessions}{9}%
\contentsline {chapter}{\numberline {4}Views}{11}%
\contentsline {section}{\numberline {4.1}View Components}{12}%
\contentsline {chapter}{\numberline {5}Variables and View Data Sources}{15}%
\contentsline {chapter}{\numberline {6}Forms}{17}%
\contentsline {chapter}{\numberline {7}Image Library}{19}%
\contentsline {chapter}{\numberline {8}Work Flow Networks}{21}%
\contentsline {section}{\numberline {8.1}Work Flow Units}{21}%
\contentsline {section}{\numberline {8.2}Work Flow Queues}{22}%
\contentsline {subsection}{\numberline {8.2.1}Action Queues}{22}%
\contentsline {subsection}{\numberline {8.2.2}External Queues}{22}%
\contentsline {subsection}{\numberline {8.2.3}Decision Queues}{22}%
\contentsline {subsection}{\numberline {8.2.4}Wait Queues}{22}%
\contentsline {subsection}{\numberline {8.2.5}Process Queues}{22}%
\contentsline {section}{\numberline {8.3}Permanent Work Flow Procedures}{22}%
\contentsline {subsection}{\numberline {8.3.1}Administration Work Flow Procedures}{22}%
\contentsline {subsection}{\numberline {8.3.2}Initial Transaction Work Flow Procedure}{23}%
\contentsline {chapter}{\numberline {9}Requests}{25}%
\contentsline {section}{\numberline {9.1}Microservice Methods}{25}%
\contentsline {chapter}{\numberline {10}Defining URL, Links and Deep Links}{27}%
\contentsline {chapter}{\numberline {11}Business Entities}{29}%
\contentsline {chapter}{\numberline {12}Libraries}{31}%
\contentsline {chapter}{\numberline {13}Server Directory Structure}{33}%
\contentsline {chapter}{\numberline {14}ServerCore Network Platform}{35}%
\contentsline {section}{\numberline {14.1}Transaction Life Cycle}{35}%
\contentsline {chapter}{\numberline {15}User Interfaces and Tools}{37}%
\contentsline {section}{\numberline {15.1}View Layout Editor}{37}%
\contentsline {section}{\numberline {15.2}Business Entity Editor}{37}%
\contentsline {section}{\numberline {15.3}Storyboard Editor}{38}%
\contentsline {chapter}{\numberline {16}Views and User Interface Components}{39}%
\contentsline {section}{\numberline {16.1}View Hierarchy}{39}%
\contentsline {chapter}{\numberline {17}JET Tag Reference}{41}%
\contentsline {section}{\numberline {17.1}CALL}{42}%
\contentsline {section}{\numberline {17.2}COMMENT}{42}%
\contentsline {section}{\numberline {17.3}DATABASE}{42}%
\contentsline {section}{\numberline {17.4}EXCLUDE}{42}%
\contentsline {section}{\numberline {17.5}EXTRACT}{42}%
\contentsline {section}{\numberline {17.6}FOR}{42}%
\contentsline {section}{\numberline {17.7}IF.. ELSE}{42}%
\contentsline {section}{\numberline {17.8}IFNOROW... ELSE}{42}%
\contentsline {section}{\numberline {17.9}IFROW... ELSE}{42}%
\contentsline {section}{\numberline {17.10}INCLUDE}{42}%
\contentsline {section}{\numberline {17.11}SYSTEM}{42}%
\contentsline {section}{\numberline {17.12}TAG}{42}%
\contentsline {section}{\numberline {17.13}WHILE}{42}%
\contentsline {section}{\numberline {17.14}WHILEROW}{42}%