|A value of a Dlg type represents a dialogue between the user and the
application, after which the application builds a value of type a. The
trivial case is that the value is already known. Alternatively, it may be
that there is some action to be performed, or else that the user needs to
be asked or told something.
|A value of Page type represents a way of rendering a page, given a request URI
that should be used for subsequent requests in order to reassociate them with the
|Converts methods for rendering and parsing the result of a page into a
|A DialogueManager is responsible for maintaining the state for Dlg
sequences for all users. To do this, it keeps for each user a session
object encapsulating their dialogues, and associates each user with their
session using cookies.
|Create a new DialogueManager to manage a set of dialogues in the web
application. This also spawns the session reaper, which cleans up sessions
that haven't been touched for a given time period.
|Closes a DialogueManager, which will cause it to cease accepting any
incoming requests, and also to terminate the session reaper thread.
|The dialogue function builds a ServerPartT that handles a given
dialogue. In general, it can be combined in normal ways with guards and
such, so long as changes in the request parameters won't cause it to be
missed when future requests are made in the same dialogue.
|Produced by Haddock version 2.6.0|