does some processing, stuffs it's results in a connection specific
datastructure and calls "rp_serve_abstract_file $template_path" at the
The template at $template_path relies on the connection specific data
to be present, assuming that the index.vuh has been processed before.
The code worked fine until I moved it to another server, where most
page calls for the same url that followed shortly after the first one
failed because the connection specific data was not present. The
reason for this turned out to be that PerformanceModeP (acs-kernel)
was set to 1 on that other server, which does the following according
to the parameter's description:
"Setting this to 1 will tell the request processor to make the
assumption that once a url is mapped to a file, that mapping never
changes. This obviously would cause problems on a development system,
but will improve performance on a production server."
So I wonder, if I (and ETP) use the rp_serve_abstract_file wrongly, by
assuming that the page it is in is never skipped or if that is a bug
in the request processor.