Yes, I configured Google App Engine to serve a frameset, and it would
properly serve up the individual pages in the frame ... at least on
the dev server. I haven't tried it on the real thing yet.
It's tricky to configure that 'app.yaml' file to do anything out-of-
the-ordinary,
but you can get it to work, with a little patience, and some
understanding of how the web server works.
Below is part of my trivial configuration to serve a frameset.
It assumes
(a) all the HTML bits are in a sub-directory named 'frameset';
(b) you have a working GAE application that can render a 'sidemenu'
for a menu in the 'MenuFrame' on the left side, and can
'serve_some_content' for the 'ContentFrame'.
<HTML>
<HEAD>
<TITLE>Sample Frameset served by Google App Engine</TITLE>
</HEAD>
<FRAMESET ROWS="140px,*" COLS="190px,*"
FRAMEBORDER=NO FRAMESPACING=0 BORDER=0 MARGINWIDTH=2
MARGINHEIGHT=2 >
<FRAME SRC="/frameset/logo.html" NAME=LogoFrame>
<FRAME SRC="/frameset/title.html" NAME=TitleFrame>
<FRAME SRC="/sidemenu" NAME=MenuFrame>
<FRAME SRC="/serve_some_content" NAME=ContentFrame>
<NOFRAMES>Error: FRAMES aren't working. Check your browser settings.
</NOFRAMES>
</FRAMESET>
</HTML>
and here's the contents of app.yaml:
application: frameset-test
version: 1
runtime: python
api_version: 1
handlers:
- url: /frameset
static_dir: frameset
- url: /.*
script: main.py
##########
Now .. just because we can do it, doesn't mean we should do it.
There are a lot of good reasons *not* to use framesets. Do you really
need a frameset?
Garrett Davis