Services

Services play a crucial role in the goval protocol, they provide the implementation for everything that a goval server can do.¹ Some services let their channels be attached to by multiple clients, while others don't let that happen. If they allow multiple clients to attach they normally have a well-known channel name, that will be indicated on it's page.

The most important service is channel 0, this is a special service that provides the opening and closing of other channels, it is usually not implemented as a service but just directly implemented in the function that handles messages. It is the only service here that a new channel cannot be created with, as it exists only as the channel with id 0 for every client.

All the currently documented services:

• Channel 0 - Manages channels, and pongs pings.
• Chat - Now only used for .draw file multiplayer, but used to power repl chat.
• OT - Powers file editing. (docs are a WIP)
• Goval Ident (unofficial) - A unofficial protocol for identifying the goval server you are connected to.

All the currently undocumented services²:

• Shellrun2 - Powers the console tab.
• Shell - Powers the shell tab.
• Exec - Let's the client run commands. Powers the git pane, as well as the resource pane.
• GCSFile - Powers the filetree.
• FSEvents - Let's the client know of file modification events.
• dotreplit - Lets the editor read and edit the state of the .replit file.
• toolchain - Lets the client know what LSP's, package managers, debuggers, and run commands are available.
• LSP - Powers code intelligence.
• Presence - Let's the client know who else is in the repl, and what file they are in.
• Audio - Powers non-VNC audio in repls.
• Snapshot - Let's the client tell the server when to snapshot and persist all file changes.
• Packager3 - Powers the packager tab.
• Socket - Opens a TCP/UDP socket in the container, rarely ever used.