Hi Marco,
your approach sounds great. It would be a very, very great help, to see some snippets :-) so the picture becomes more clear for me.
Ciao, Günter
P.S.: Sorry for the second email, I didn't send it to the mailing-list
Am 08.04.2016 um 09:13 schrieb Marco Lettere m.lettere@gmail.com:
Hi Günter, we have worked on several web applications that include a frontend and we are very happy with using basex for serving both static (scripts, css, images) and dynamic (markup) content. One pattern that we've used often and that we find very productive is to split markup content into different .xqm modules. The modules are called through the xquery:invoke function in order to "explode" their output into the main page. In our opinion this is a good approach because it is applicable recursively to sub-modules. Content of modules may be dynamic as well and parametric values are passed into the module through external variables. Finally, it is possible to set up an automatic way of mapping requests to module invocations by exploiting REST path segments for example. I hope I have been able to explain it well enough otherwise, just let me know and as soon as possible I'll provide an example code snippet that demonstrates the approach.
Ciao, Marco.
On 07/04/2016 17:08, Günter Dunz-Wolff wrote:
Hi,
I'm planning to relaunch my website (kleist-digital.de) with OpenShift as BaseX-Server. After some difficulties and a lot of help from Christian and Andy the server is running now.
I took a look at RESTXQ and it seems quite interesting to build the whole frontend for my app with it. Some questions I have:
I'm working with a basic layout for all pages. This basic layout-file includes header, footer and changing content. What is the best approach with RESTXQ. How to build a modular concept with RESTXQ?
Is there any site-structure preferred?
Most of the site is dynamic. But I need also static files like images, css, javascript. Where to put them best (so that the Openshift-Server can handle them)?
Thanks for any advice and help.
Günter