After 5.0.2, the Web Server had a backwards incompatible change that prevents X-expressions and lists of bytes from being directly returned from servlets. Please read "PLTHOME/collects/web-server/compat/0/README" to learn about porting your servlets forward. Don’t worry. It’s easy.
Templates are compiled into your application, so when you change them there is no connection between that change in the filesystem and the compiled bytecode that is already loaded in a running Web server process. For more discussion, see Why are my stateful servlets not updating on the server when I change the file on disk?.
If you are using serve/servlet, it starts a Web server that directly references a closure that has no connection to some file on the disk.
If you are using the command-line tool, or configuration file, then by default, the server uses make-cached-url->servlet to load servlets from the disk. As it loads them, they are cached and the disk is not referred to for future requests. This ensures that there is a single namespace for each servlet, so that different instances can share resources, such as database connections, and communicate through the store. The default configuration of the server (meaning the dispatcher sequence used when you load a configuration file) provides a special URL to localhost that will reset the cache: "/conf/refresh-servlets".
If you want the server to reload your changed servlet code, then GET this URL and the server will reload the servlet on the next request. However, you may be surprised by what happens on the next request. For more discussion, see After refreshing my stateful servlet, old captured continuations don’t change or old global effects are gone. Why?.
10.5 After refreshing my stateful servlet, old captured continuations don’t change or old global effects are gone. Why?
Every load of your servlet is in a fresh namespace. When you refresh, a new namespace without the old effects is created. Old captured continuations refer to the original namespace and will never update. It is impossible, in general, to port a continuation from one namespace to another, because the code could be arbitrarily different.
Continuations are serialized with a hash that ensures that any source code modifications makes all the old continuations incompatible for the same reason native continuations naturally are.
However, this hash only protects against changes in a single source file. Therefore if you modularize your application, then only continuations that refer to changed source files will be incompatible. For example, if you put all your templates in a single module, then it can change without invalidating old continuations.
The biggest problem is that a naive usage of continuations will allow continuations to subvert authentication mechanisms. Typically, all that is necessary to execute a continuation is its URL. Thus, URLs must be as protected as the information in the continuation.
Consider if you link to a public site from a private continuation URL: the Referrer field in the new HTTP request will contain the private URL. Furthermore, if your HTTP traffic is in the clear, then these URLs can be easily poached.
One solution to this is to use a special cookie as an authenticator. This way, if a URL escapes, it will not be able to be used, unless the cookie is present. For advice about how to do this well, see Dos and Don’ts of Client Authentication on the Web from the MIT Cookie Eaters.
Note: It may be considered a great feature that URLs can be shared this way, because delegation is easily built into an application via URLs.
For example, XML allows the "empty tag shorthand", e.g. <img src='...' />, on every tag, while HTML occasionally requires an end tag, e.g. TEXTAREA. Similarly, XML allows an end tag, e.g. <img src='...'></img>, on every tag, while HTML occasionally forbides an end tag, e.g. IMG. (Of course, browsers do not necessarily implement their HTML parsing as specified and may be more or less lenient towards XML-like HTML, so your test browser may not treat these forms as problematic.)
Since the Web Server uses xml to format X-expressions, it inherits xml’s default rendering behavior in general and its use of "empty tag shorthand" in particular. xml’s default is always use the shorthand with the tags from html-empty-tags and never otherwise. This list should contain the W3C’s approved list. You can change it with the empty-tag-shorthand parameter.
You can also change your X-expression so that an end tag is forced. For example, '(textarea [(name "text")]) renders as <textarea name="text" />, while '(textarea [(name "text")] "") renders as <textarea name="text"></textarea>, because of the string content in the X-expression. In this case, the end tag will always be present regardless of the value of empty-tag-shorthand. It is not possible to force the other possibility; i.e., never include an end tag.
You may think the Web Server could do a better job advertising that the contents it serves is more like XML by default. Unfortunately, browser support for such advertisement is lacking. You can use response/xexpr to easily customize your application’s MIME type and response headers.
Finally, you may find Web browser inspectors such as the Safari Inspector, Firebug, and the Google Chrome error console to be useful tools in identifying offending tags.
(define (main-page logged-in?) (define user-content (if logged-in? (include-template "user-info.html") (include-template "auth.html"))) (include-template "site.html"))
.... user-content ....
This allows you to do the same thing but is safer and more efficient: safer because there is no way to include templates that are not named by the programmer and more efficient because all the templates are compiled (and optimized) with the rest of the code.
If you insist on dynamicism, there is always eval.