Ah, should have seen that in your original post.
Yeah, you'll just have to duplicate the pages, having a normal page
for standard links, and a 'content only' page for ajax calls.
Not much else you can do without a server to build the html for you on
the fly :-/
On Mar 25, 1:32 pm, zwaldowski <[
This website is essentially for a contest. I'm working with a couple
of friends on a historical competition. The genius historians that
run the competetion's website division think they're next-gen by
requiring you to put an HTML site on a CD. So, no. :-D
On Mar 24, 3:57 pm, Hamish Campbell <
> However, taking this approach
> would have multiple headers and
> footers. How should I go about this?
If you're using plain HTML then yes, you'll need to duplicate the
header/footer data in the "fall back" pages.
Do you have a database and/or server-side scripting language at your
disposal?
Hi,
I have not understood your examples, but the classical approach with
ajax, from a
server side point of view, is to send the content of the page with
header and footer if it is
an http request and to send only the content if it is ajax.
I think that you can detect an ajax call from the head
4 matches
Mail list logo
