Add xrefs and advice re Robby
This commit is contained in:
parent
0cbf694468
commit
2bd19d1604
|
@ -22,13 +22,13 @@ A stateless servlet should @racket[provide] the following exports:
|
|||
}
|
||||
|
||||
@defthing[stuffer (stuffer/c serializable? bytes?)]{
|
||||
This is the stuffer that will be used for the servlet.
|
||||
This is the @tech{stuffer} that will be used for the servlet.
|
||||
|
||||
If it is not provided, it defaults to @racket[default-stuffer].
|
||||
}
|
||||
|
||||
@defthing[manager manager?]{
|
||||
This is the manager that will be used for the servlet.
|
||||
This is the @tech{manager} that will be used for the servlet.
|
||||
|
||||
If it is not provided, it defaults to @racket[(create-none-manager #f)].
|
||||
}
|
||||
|
|
|
@ -8,7 +8,7 @@ up memory on the server. Furthermore, garbage collection can not be used
|
|||
to free this memory, because there are roots outside the system: users'
|
||||
browsers, bookmarks, brains, and notebooks. Therefore, some other strategy
|
||||
must be used if memory usage is to be controlled. This functionality is
|
||||
pluggable through the manager interface.
|
||||
pluggable through the @deftech{manager} interface.
|
||||
|
||||
@; ------------------------------------------------------------
|
||||
@section[#:tag "manager"]{General}
|
||||
|
|
|
@ -19,7 +19,7 @@ A stateful servlet should @racket[provide] the following exports:
|
|||
}
|
||||
|
||||
@defthing[manager manager?]{
|
||||
The manager for the continuations of this servlet. See @secref["managers"] for options.
|
||||
The @tech{manager} for the continuations of this servlet. See @secref["managers"] for options.
|
||||
}
|
||||
|
||||
@defproc[(start [initial-request request?])
|
||||
|
|
|
@ -1,6 +1,7 @@
|
|||
#lang scribble/doc
|
||||
@(require "web-server.rkt"
|
||||
(for-label racket/serialize
|
||||
web-server/lang/stuff-url
|
||||
web-server/lang/abort-resume
|
||||
web-server/lang/web))
|
||||
|
||||
|
@ -49,9 +50,12 @@ Second, the defunctionalization process is sensitive to the syntactic
|
|||
structure of your program. Therefore, if you change your program in a
|
||||
trivial way, for example, changing a constant, then all serialized
|
||||
continuations will be obsolete and will error when deserialization is
|
||||
attempted. This is a feature, not a bug! It is a small price to pay for
|
||||
protection from the sorts of errors that would occur if your program
|
||||
were changed in a meaningful way.
|
||||
attempted. This is a feature, not a bug! It is a small price to pay
|
||||
for protection from the sorts of errors that would occur if your
|
||||
program were changed in a meaningful way. If you use the
|
||||
@racket[default-stuffer] or @racketmodname[web-server/stuffers/hash],
|
||||
then whenever you change your servlet's code, you can safely delete
|
||||
all saved continuations, because they won't be used any longer.
|
||||
|
||||
Third, the values in the lexical scope of your continuations must be
|
||||
serializable for the continuations itself to be serializable. This means
|
||||
|
|
Loading…
Reference in New Issue
Block a user