@@ -1,7 +1,7 @@
1−% WAI-MW.tex
2−\begin{hcarentry}{WAI}
1+% WAI-KW.tex
2+\begin{hcarentry}[updated]{WAI}
33\label{wai}
4−\report{Kazu Yamamoto}%05/16
4+\report{Kazu Yamamoto}%11/16
55\participants{Michael Snoyman, Greg Weber}
66\status{stable}
77\makeheader
@@ -11,7 +11,10 @@ between web applications and handlers in Haskell.
1111The \texttt{Application} data type is defined as follows:
1212
1313\begin{verbatim}
14−type Application = Request -> (Response -> IO ResponseReceived) -> IO ResponseReceived
14+type Application
15+ = Request
16+ -> (Response -> IO ResponseReceived)
17+ -> IO ResponseReceived
1518\end{verbatim}
1619
1720That is, a WAI application takes two arguments: a \texttt{Request} and
@@ -33,10 +36,10 @@ WebSocket (wai-websocket) and Event Source (wai-extra)
3336can be implemented, too.
3437
3538It is possible to develop WAI applications directly.
36−For instance, Hoogle and Mighttpd2~\cref{mighttpd2} take this way.
39+For instance, Hoogle and Mighttpd2 take this way.
3740However, you may want to use web application frameworks
38−such as Apiary, MFlow~\cref{mflow}, rest, Servant, Scotty~\cref{scotty}, Spock,
39−Yesod~\cref{yesod}, etc.
41+such as Apiary, MFlow, rest, Servant, Scotty, Spock,
42+Yesod, etc.
4043
4144WAI also provides \texttt{Middleware}:
4245
@@ -46,10 +49,7 @@ type Middleware = Application -> Application
4649
4750WAI middleware can inspect and transform a request, for example by automatically gzipping a response or logging a request (wai-extra).
4851
49−Since the last HCAR, WAI has successfully released version 3.2,
50−which removes the experimental HTTP/2 module and some APIs.
51−We bumped the version from 3.0 to 3.2 for consistency with
52−Warp 3.2.
52+Since the last HCAR, no major changes were made.
5353
5454\FurtherReading
5555\begin{compactitem}