comparison doc/manual.tex @ 1335:79557535b843

-prefix command-line option
author Adam Chlipala <adam@chlipala.net>
date Sun, 12 Dec 2010 10:44:19 -0500
parents dab85a49e0ab
children 660a2715e2bd
comparison
equal deleted inserted replaced
1334:a1aa62b472cf 1335:79557535b843
236 236
237 \item \texttt{-output FILENAME}: Set where the application executable is written. 237 \item \texttt{-output FILENAME}: Set where the application executable is written.
238 238
239 \item \texttt{-path NAME VALUE}: Set the value of path variable \texttt{\$NAME} to \texttt{VALUE}, for use in \texttt{.urp} files. 239 \item \texttt{-path NAME VALUE}: Set the value of path variable \texttt{\$NAME} to \texttt{VALUE}, for use in \texttt{.urp} files.
240 240
241 \item \texttt{-prefix PREFIX}: Equivalent to the \texttt{prefix} directive from \texttt{.urp} files
242
241 \item \texttt{-protocol [http|cgi|fastcgi]}: Set the protocol that the generated application speaks. 243 \item \texttt{-protocol [http|cgi|fastcgi]}: Set the protocol that the generated application speaks.
242 \begin{itemize} 244 \begin{itemize}
243 \item \texttt{http}: This is the default. It is for building standalone web servers that can be accessed by web browsers directly. 245 \item \texttt{http}: This is the default. It is for building standalone web servers that can be accessed by web browsers directly.
244 246
245 \item \texttt{cgi}: This is the classic protocol that web servers use to generate dynamic content by spawning new processes. While Ur/Web programs may in general use message-passing with the \texttt{send} and \texttt{recv} functions, that functionality is not yet supported in CGI, since CGI needs a fresh process for each request, and message-passing needs to use persistent sockets to deliver messages. 247 \item \texttt{cgi}: This is the classic protocol that web servers use to generate dynamic content by spawning new processes. While Ur/Web programs may in general use message-passing with the \texttt{send} and \texttt{recv} functions, that functionality is not yet supported in CGI, since CGI needs a fresh process for each request, and message-passing needs to use persistent sockets to deliver messages.