Goran Rakic wrote: > > Alternatively, we can avoid the CGI and just SSI include a > > static file of links. This file can be generated by libgo after it > > knows exactly which languages built. > > What is performance penalty for using SSI? If we can tolerate that, this > can work really nice.
I have been testing this; results on my laptop (eog index.html.en page), tested with ab -t 30 Requests per second: 3251.86 [#/sec] (mean) Then I added four includes[1] and did the same test: Requests per second: 1521.55 [#/sec] (mean) It sure drops but it is still way faster than necessary, I guess. [1] - at the end of </head> to link to an external stylesheet, I believe we should modify the xsl files so they don't generate any CSS. (cf db2html-css.xsl) - after <body>, to include a header with title, logos, general navigation links (About GNOME...) - before </body>, to include a table of content - and another one to include a standard footer (GNOME and the foot logos are trademarks...) As for TOC files, they are basically: <ul> <li><a href="index.html.en">Image Viewer Manual</a></li> <li><a href="eog-introduction.html.en">Introduction</a></li> <li><a href="eog-whenyoustart.html.en">Getting Started</a></li> <li><a href="eog-view.html.en">Viewing Images</a></li> <li><a href="eog-manipulate.html.en">Manipulating Images</a></li> <li><a href="eog-save-rename.html.en">Saving</a></li> <li><a href="eog-prefs.html.en">Preferences</a></li> </ul> Is this possible to have xsltproc generate such a file along the others or would it need another call ? Work in progress, still needs language links: http://lgo.0d.be/eog/2.16/ TOC file, included: http://lgo.0d.be/eog/2.16/nav.html.en (or .fr) Frederic _______________________________________________ gnome-web-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-web-list
