Hello,
Now the router is working very efficiently:
There are 2 hash tables.
One for the ROUTE (hRouting) and one for the WebPageName (hWebPageName).
First the CONTROLLER checks whether the user is authorized and then forwards the request to the ROUTER.
In practice, only these two queries are required in the ROUTER:
cRoute: = hb_HGetDef (hRouting, hashkey, 'home')
cWebPageName: = hb_HGetDef (hWebPageName, hashkey, 'home')
return View( cRoute ) from ROUTER
then does the work.
I'm using the GENESIS example from mod harbour.
Best regards,
Otto
Now the router is working very efficiently:
There are 2 hash tables.
hRouting[ "datakunden:edit" ] = "edit"
hRouting[ "datakunden:brief" ] = "briefe"
...
hRouting[ "landingpage:edit" ] = "editbutton"
...
hWebPageName[ "landingpage:edit" ] = "Setup Schalter Landing Page"
hWebPageName[ "datakunden:brief" ] = "QRCode Notes"
hWebPageName[ "qrcode" ] = "QRCode Verwaltung"
hWebPageName[ "landing" ] = "Langing Page Generator"One for the ROUTE (hRouting) and one for the WebPageName (hWebPageName).
First the CONTROLLER checks whether the user is authorized and then forwards the request to the ROUTER.
In practice, only these two queries are required in the ROUTER:
cRoute: = hb_HGetDef (hRouting, hashkey, 'home')
cWebPageName: = hb_HGetDef (hWebPageName, hashkey, 'home')
return View( cRoute ) from ROUTER
then does the work.
I'm using the GENESIS example from mod harbour.
Best regards,
Otto