A
Aaron Watters
Hi folks. I just modified the WHIFF concepts index page
http://aaron.oirt.rutgers.edu/myapp/docs/W1000.concepts
To include the following paragraph with a startling and arrogant
claim in the final sentence
"""
Developers build WHIFF applications much like they build
static web content, PHP applications, JSP pages, or ASP
pages among others -- the developer "drops" files into a
directory, and the files are automatically used to respond
to URLs related to the filename.
**This intuitive and ubiquitous approach to organizing
web components is not automatically supported by other
WSGI infrastructures.**
"""
[I go on to illustrate the concept with examples...]
Is the final sentence true? Are there other WSGI approach
which make deploying a dynamic page as easy as putting
an HTML file in a static directory? If I'm lying I'd like to
correct the statement and my knowledge of what else is out
there is faulty and incomplete, so please correct me.
Thanks, -- Aaron Watters
===
less is more
http://aaron.oirt.rutgers.edu/myapp/docs/W1000.concepts
To include the following paragraph with a startling and arrogant
claim in the final sentence
"""
Developers build WHIFF applications much like they build
static web content, PHP applications, JSP pages, or ASP
pages among others -- the developer "drops" files into a
directory, and the files are automatically used to respond
to URLs related to the filename.
**This intuitive and ubiquitous approach to organizing
web components is not automatically supported by other
WSGI infrastructures.**
"""
[I go on to illustrate the concept with examples...]
Is the final sentence true? Are there other WSGI approach
which make deploying a dynamic page as easy as putting
an HTML file in a static directory? If I'm lying I'd like to
correct the statement and my knowledge of what else is out
there is faulty and incomplete, so please correct me.
Thanks, -- Aaron Watters
===
less is more