In any case, if you didn't know, I've been working on a templating
system on my free time. The actual question I have is the last
paragraph. The rest is just background info.
So, the templating system has a serverside component, which is somewhat
done insofar as it relates to a template development interface. It's not
so much done as far as a consistent and reliable interface with
different systems of page organization.
Essentially you have two useful functions that interface with a
hierarchical structure (part of the filesystem) to determine what needs
to be loaded.
--Where leafCn is the common name of the template part you want to use:
---ex. useleaf(leafCn) will check if leafCn.php exists in the template's
path, and if not, it will try the parent path, and so on until it
reaches what has been configured to be the root template path.
--Where templateDn is the path to the template you're currently loading
template parts from.
--This would be used in the leafCn.php file of a higher-level directory.
Essentially it means that the use the leaf from the next template parent
directory where that leaf exists.
The clientside component is fairly consistent in it's interface with the
server. The sole purpose of the clientside component is to swap out the
minimum template parts (at least so much as it's feasible).
So in essence, you load the page, and if AJAX works, relevant links will
the template that change between the current page, and the page being
requested. Yes, even the head element (which can't have an ID).
Then you can also say (not implemented yet), update this one part of the
There is a problem with the AJAX portion however. If you think it's
browsing history and modifying the location bar: not quite. You can
actually do this via a hack by changing the # delimiter.
However, there is a limitation to this: the AJAX permalink would have to
Why is this? The # does not change the current page at all, so it's
considered secure, and can be changed without forcing a GET request.
I was wondering if anyone had any ideas on how a browser implementation
might be possible to ensure security from phishing schemes AND allow a
normal permalink to load into the navigation bar upon an XMLHttpRequest