Package socket

Overview ▹

Overview ▾

Package socket implements an WebSocket-based playground backend.
Clients connect to a websocket handler and send run/kill commands, and
the server sends the output and exit status of the running processes.
Multiple clients running multiple processes may be served concurrently.
The wire format is JSON and is described by the Message type.

This will not run on App Engine as WebSockets are not supported there.

Index ▹

Index ▾

Package files

Internal call graph ▹

Internal call graph ▾

In the call graph viewer below, each node
is a function belonging to this package
and its children are the functions it
calls—perhaps dynamically.

The root nodes are the entry points of the
package: functions that may be called from
outside the package.
There may be non-exported or anonymous
functions among them if they are called
dynamically from another package.

Click a node to visit that function's source code.
From there you can visit its callers by
clicking its declaring func
token.

Functions may be omitted if they were
determined to be unreachable in the
particular programs or tests that were
analyzed.

Variables

Environ provides an environment when a binary, such as the go tool, is
invoked.

var Environ func() []string = os.Environ

RunScripts specifies whether the socket handler should execute shell scripts
(snippets that start with a shebang).