File: service.Rd

package info (click to toggle)
r-cran-httpuv 1.6.15%2Bdfsg-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 1,292 kB
  • sloc: ansic: 6,499; cpp: 5,501; makefile: 103; sh: 56
file content (39 lines) | stat: -rw-r--r-- 1,338 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
% Generated by roxygen2: do not edit by hand
% Please edit documentation in R/httpuv.R
\name{service}
\alias{service}
\title{Process requests}
\usage{
service(timeoutMs = ifelse(interactive(), 100, 1000))
}
\arguments{
\item{timeoutMs}{Approximate number of milliseconds to run before returning.
It will return this duration has elapsed. If 0 or Inf, then the function
will continually process requests without returning unless an error occurs.
If NA, performs a non-blocking run without waiting.}
}
\description{
Process HTTP requests and WebSocket messages. If there is nothing on R's call
stack -- if R is sitting idle at the command prompt -- it is not necessary to
call this function, because requests will be handled automatically. However,
if R is executing code, then requests will not be handled until either the
call stack is empty, or this function is called (or alternatively,
\code{\link[later]{run_now}} is called).
}
\details{
In previous versions of httpuv (1.3.5 and below), even if a server created by
\code{\link{startServer}} exists, no requests were serviced unless and until
\code{service} was called.

This function simply calls \code{\link[later]{run_now}()}, so if your
application schedules any \code{\link[later]{later}} callbacks, they will be
invoked.
}
\examples{
\dontrun{
while (TRUE) {
  service()
}
}

}