\HeaderA{connections}{Functions to Manipulate Connections}{connections}
\aliasA{bzfile}{connections}{bzfile}
\aliasA{close}{connections}{close}
\methaliasA{close.connection}{connections}{close.connection}
\aliasA{connection}{connections}{connection}
\aliasA{fifo}{connections}{fifo}
\aliasA{file}{connections}{file}
\aliasA{flush}{connections}{flush}
\methaliasA{flush.connection}{connections}{flush.connection}
\aliasA{gzfile}{connections}{gzfile}
\aliasA{isIncomplete}{connections}{isIncomplete}
\aliasA{isOpen}{connections}{isOpen}
\aliasA{open}{connections}{open}
\methaliasA{open.connection}{connections}{open.connection}
\aliasA{pipe}{connections}{pipe}
\aliasA{print.connection}{connections}{print.connection}
\aliasA{socketConnection}{connections}{socketConnection}
\aliasA{summary.connection}{connections}{summary.connection}
\aliasA{unz}{connections}{unz}
\aliasA{url}{connections}{url}
\keyword{file}{connections}
\keyword{connection}{connections}
\begin{Description}\relax
Functions to create, open and close connections.
\end{Description}
\begin{Usage}
\begin{verbatim}
file(description = "", open = "", blocking = TRUE,
     encoding = getOption("encoding"))

pipe(description, open = "", encoding = getOption("encoding"))

fifo(description = "", open = "", blocking = FALSE,
     encoding = getOption("encoding"))

gzfile(description, open = "", encoding = getOption("encoding"),
       compression = 6)

unz(description, filename, open = "",
    encoding = getOption("encoding"))

bzfile(description, open = "", encoding = getOption("encoding"))

url(description, open = "", blocking = TRUE,
    encoding = getOption("encoding"))

socketConnection(host = "localhost", port, server = FALSE,
                 blocking = FALSE, open = "a+",
                 encoding = getOption("encoding"))

open(con, ...)
## S3 method for class 'connection':
open(con, open = "r", blocking = TRUE, ...)

close(con, ...)
## S3 method for class 'connection':
close(con, type = "rw", ...)

flush(con)

isOpen(con, rw = "")
isIncomplete(con)
\end{verbatim}
\end{Usage}
\begin{Arguments}
\begin{ldescription}
\item[\code{description}] character. A description of the connection. For
\code{file} and \code{pipe} this is a path to the file to be opened.
For \code{url} it is a complete URL, including schemes
(\code{http://}, \code{ftp://} or \code{file://} -- see Details).
\code{file} also accepts complete URLs.

\item[\code{filename}] a filename within a zip file.
\item[\code{con}] a connection.
\item[\code{host}] character.  Host name for port.
\item[\code{port}] integer.  The TCP port number.
\item[\code{server}] logical.  Should the socket be a client or a server?
\item[\code{open}] character.  A description of how to open the connection
(if at all).  See Details for possible values.
\item[\code{blocking}] logical.  See the \sQuote{Blocking} section below.
\item[\code{encoding}] The name of the encoding to be used.  See the
\sQuote{Encoding} section below.
\item[\code{compression}] integer in 0--9.  The amount of compression to be
applied when writing, from none to maximal.  The default is a good
space/time compromise.
\item[\code{type}] character. Currently ignored.
\item[\code{rw}] character.  Empty or \code{"read"} or \code{"write"},
partial matches allowed.
\item[\code{...}] arguments passed to or from other methods.
\end{ldescription}
\end{Arguments}
\begin{Details}\relax
The first eight functions create connections.  By default the
connection is not opened (except for \code{socketConnection}), but may
be opened by setting a non-empty value of argument \code{open}.

\code{gzfile} applies to files compressed by \file{gzip}, and
\code{bzfile} to those compressed by \file{bzip2}.  \code{gzfile} can
also open uncompressed files.  In each case the actual file is opened
in binary mode and so no translations are done if the original file
was a text file.

\code{unz} reads (only) single files within zip files, in binary mode.
The description is the full path, with \file{.zip} extension if required.

All platforms support \code{file}, \code{gzfile}, \code{bzfile},
\code{unz} and \code{url("file://")} connections.  The other types may
be partially implemented or not implemented at all.  (They do work on
most Unix platforms, and all but \code{fifo} on Windows.)

Proxies can be specified for \code{url} connections: see
\code{\LinkA{download.file}{download.file}}.

\code{open}, \code{close} and \code{seek} are generic functions: the
following applies to the methods relevant to connections.

\code{open} opens a connection.  In general functions using
connections will open them if they are not open, but then close them
again, so to leave a connection open call \code{open} explicitly.

Possible values for the mode \code{open} to open a connection are
\describe{
\item[\code{"r"} or \code{"rt"}] Open for reading in text mode.
\item[\code{"w"} or \code{"wt"}] Open for writing in text mode.
\item[\code{"a"} or \code{"at"}] Open for appending in text mode.
\item[\code{"rb"}] Open for reading in binary mode.
\item[\code{"wb"}] Open for writing in binary mode.
\item[\code{"ab"}] Open for appending in binary mode.
\item[\code{"r+"}, \code{"r+b"}] Open for reading and writing.
\item[\code{"w+"}, \code{"w+b"}] Open for reading and writing,
truncating file initially.
\item[\code{"a+"}, \code{"a+b"}] Open for reading and appending.
}
Not all modes are applicable to all connections: for example URLs can
only be opened for reading.  Only file and socket connections can be
opened for reading and writing/appending.
For many connections there is little or no
difference between text and binary modes, but there is for file-like
connections on Windows, and \code{\LinkA{pushBack}{pushBack}} is text-oriented and
is only allowed on connections open for reading in text mode.

\code{close} closes and destroys a connection.

\code{flush} flushes the output stream of a connection open for
write/append (where implemented).

If for a \code{file} connection the description is \code{""}, the file
is immediately opened (in \code{"w+"} mode unless \code{open="w+b"} is
specified) and unlinked from the file system.  This provides a
temporary file to write to and then read from.

A note on \code{file://} URLs.  The most general form (from RFC1738) is
\code{file://host/path/to/file}, but \R{} only accepts the form with an
empty \code{host} field referring to the local machine.
This is then \code{file:///path/to/file}, where \code{path/to/file} is
relative to \code{/}.  So although the third slash is strictly part of
the specification not part of the path, this can be regarded as a way
to specify the file \file{/path/to/file}.  It is not possible to
specify a relative path using a file URL.
Also, no attempt is made to decode an encoded URL: call
\code{\LinkA{URLdecode}{URLdecode}} if necessary.
\end{Details}
\begin{Value}
\code{file}, \code{pipe}, \code{fifo}, \code{url}, \code{gzfile},
\code{bzfile}, \code{unz} and \code{socketConnection} return a
connection object which inherits from class \code{"connection"} and
has a first more specific class.

\code{isOpen} returns a logical value, whether the connection is
currently open.

\code{isIncomplete} returns a logical value, whether last read attempt
was blocked, or for an output text connection whether there is
unflushed output.
\end{Value}
\begin{Section}{Encoding}
\strong{Note:} prior to \R{} 2.1.0 there was a byte-by-byte encoding
option applied to input only.  This has been replaced by a more
comprehensive scheme.

The encoding of the input/output stream of a connection in \emph{text}
mode can be specified by name, in the same way as it would be given to
\code{\LinkA{iconv}{iconv}}: see that help page for how to find out what names are
recognized on your platform.  Additionally, \code{""} and
\code{"native.enc"} both mean the \sQuote{native} encoding, that is
the internal encoding of the current locale and hence no translation
is done.
Not all builds of \R{} support this, and if yours does not, specifying a
non-default encoding will give an error when the connection is opened.

Re-encoding only works for connections in text mode.

The encoding \code{"UCS-2LE"} is treated specially, as it is the
appropriate value for Windows \sQuote{Unicode} text files.  If the
first two bytes are the Byte Order Mark \code{0xFFFE} then these are
removed as most implementations of \code{\LinkA{iconv}{iconv}} do not accept
BOMs.  Note that some implementations
will handle BOMs using encoding \code{"UCS2"} but many
will not.

Exactly what happens when the requested translation cannot be done is
in general undocumented.  Requesting a conversion that is not supported is
an error, reported when the connection is opened.  On output the
result is likely to be that up to the error, with a warning.  On
input, it will most likely be all or some of the input up to the
error.

The encoding for \code{\LinkA{stdin}{stdin}} when redirected from a file can
be set by the command-line flag \code{--encoding}.
\end{Section}
\begin{Section}{Blocking}
The default condition for all but fifo and socket connections is to be in
blocking mode.  In that mode, functions do not return to the \R{}
evaluator until they are complete.   In non-blocking mode, operations
return as soon as possible, so on input they will return with whatever
input is available (possibly none) and for output they will return
whether or not the write succeeded.

The function \code{\LinkA{readLines}{readLines}} behaves differently in respect of
incomplete last lines in the two modes: see its help page.

Even when a connection is in blocking mode, attempts are made to
ensure that it does not block the event loop and hence the operation
of GUI parts of \R.  These do not always succeed, and the whole
process will be blocked during a DNS lookup on Unix, for example.

Most blocking operations on URLs and sockets are subject to the
timeout set by \code{options("timeout")}.  Note that this is a timeout
for no response at all, not for the whole operation.
\end{Section}
\begin{Section}{Fifos}
Fifos default to non-blocking.  That follows Svr4 and it probably most
natural, but it does have some implications.
In particular, opening a non-blocking fifo connection for writing
(only) will fail unless some other process is reading on the fifo.

Opening a fifo for both reading and writing (in any mode: one can only
append to fifos) connects both sides of the fifo to the \R{} process,
and provides an similar facility to \code{file()}.
\end{Section}
\begin{Section}{Clipboard}
\code{file} can also be used with \code{description = "clipboard"}
in mode \code{"r"} only.  It reads the X11 primary selection, which
can also be specified as \code{"X11\_primary"} and the secondary
selection as \code{"X11\_secondary"}.

When the clipboard is opened for reading, the contents are immediately
copied to internal storage in the connection.

Unix users wishing to \emph{write} to the primary selection may be
able to do so via \code{xclip}
(\url{http://people.debian.org/~kims/xclip/}), for example by
\code{pipe("xclip -i", "w")}.

MacOS X users can use \code{pipe("pbpaste")} and
\code{pipe("pbcopy", "w")} to read from and write to that system's
clipboard.
\end{Section}
\begin{Note}\relax
\R's connections are modelled on those in S version 4 (see Chambers,
1998).  However \R{} goes well beyond the Svr4 model, for example in
output text connections and URL, \code{gzfile}, \code{bzfile} and socket
connections.

The default mode in \R{} is \code{"r"} except for socket connections.
This differs from Svr4, where it is the equivalent of \code{"r+"},
known as \code{"*"}.

On platforms where \code{vsnprintf} does not return the needed length
of output (e.g., Windows) there is a 100,000 character output limit on
the length of line for \code{fifo}, \code{gzfile} and \code{bzfile}
connections: longer lines will be truncated with a warning.
\end{Note}
\begin{References}\relax
Chambers, J. M. (1998)
\emph{Programming with Data. A Guide to the S Language.} Springer.
\end{References}
\begin{SeeAlso}\relax
\code{\LinkA{textConnection}{textConnection}}, \code{\LinkA{seek}{seek}}, \code{\LinkA{readLines}{readLines}},
\code{\LinkA{readBin}{readBin}}, \code{\LinkA{writeLines}{writeLines}}, \code{\LinkA{writeBin}{writeBin}},
\code{\LinkA{showConnections}{showConnections}}, \code{\LinkA{pushBack}{pushBack}}.

\code{\LinkA{capabilities}{capabilities}} to see if \code{url},
\code{fifo} and \code{socketConnection} are supported by this build of \R.
\end{SeeAlso}
\begin{Examples}
\begin{ExampleCode}
zz <- file("ex.data", "w")  # open an output file connection
cat("TITLE extra line", "2 3 5 7", "", "11 13 17", file = zz, sep = "\n")
cat("One more line\n", file = zz)
close(zz)
readLines("ex.data")
unlink("ex.data")

zz <- gzfile("ex.gz", "w")  # compressed file
cat("TITLE extra line", "2 3 5 7", "", "11 13 17", file = zz, sep = "\n")
close(zz)
readLines(gzfile("ex.gz"))
unlink("ex.gz")

zz <- bzfile("ex.bz2", "w")  # bzip2-ed file
cat("TITLE extra line", "2 3 5 7", "", "11 13 17", file = zz, sep = "\n")
close(zz)
print(readLines(bzfile("ex.bz2")))
unlink("ex.bz2")

## An example of a file open for reading and writing
Tfile <- file("test1", "w+")
c(isOpen(Tfile, "r"), isOpen(Tfile, "w")) # both TRUE
cat("abc\ndef\n", file=Tfile)
readLines(Tfile)
seek(Tfile, 0, rw="r") # reset to beginning
readLines(Tfile)
cat("ghi\n", file=Tfile)
readLines(Tfile)
close(Tfile)
unlink("test1")

## We can do the same thing with an anonymous file.
Tfile <- file()
cat("abc\ndef\n", file=Tfile)
readLines(Tfile)
close(Tfile)

if(capabilities("fifo")) {
  zz <- fifo("foo", "w+")
  writeLines("abc", zz)
  print(readLines(zz))
  close(zz)
  unlink("foo")
}

## Not run: ## Unix examples of use of pipes

# read listing of current directory
readLines(pipe("ls -1"))

# remove trailing commas. Suppose
% cat data2
450, 390, 467, 654,  30, 542, 334, 432, 421,
357, 497, 493, 550, 549, 467, 575, 578, 342,
446, 547, 534, 495, 979, 479
# Then read this by
scan(pipe("sed -e s/,$// data2"), sep=",")

# convert decimal point to comma in output
# both R strings and (probably) the shell need \ doubled
zz <- pipe(paste("sed s/\\\\./,/ >", "outfile"), "w")
cat(format(round(rnorm(100), 4)), sep = "\n", file = zz)
close(zz)
file.show("outfile", delete.file=TRUE)## End(Not run)

## Not run: ## example for Unix machine running a finger daemon

con <- socketConnection(port = 79, blocking = TRUE)
writeLines(paste(system("whoami", intern=TRUE), "\r", sep=""), con)
gsub(" *$", "", readLines(con))
close(con)## End(Not run)

## Not run: ## two R processes communicating via non-blocking sockets
# R process 1
con1 <- socketConnection(port = 6011, server=TRUE)
writeLines(LETTERS, con1)
close(con1)

# R process 2
con2 <- socketConnection(Sys.info()["nodename"], port = 6011)
# as non-blocking, may need to loop for input
readLines(con2)
while(isIncomplete(con2)) {Sys.sleep(1); readLines(con2)}
close(con2)
## End(Not run)

## Not run: 
 ## examples of use of encodings
cat(x, file = file("foo", "w", encoding="UTF-8"))
# read a 'Windows Unicode' file including names
A <- read.table(file("students", encoding="UCS-2LE"))
## End(Not run)\end{ExampleCode}
\end{Examples}

