Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.awfixer.me/llms.txt

Use this file to discover all available pages before exploring further.

Use JSTime’s native TCP API to implement performance sensitive systems like database clients, game servers, or anything that needs to communicate over TCP (instead of HTTP). This is a low-level API intended for library authors and for advanced use cases.

​
Start a server (JSTime.listen())

To start a TCP server with JSTime.listen: 
JSTime.listen({
  hostname: "localhost",
  port: 8080,
  socket: {
    data(socket, data) {}, // message received from client
    open(socket) {}, // socket opened
    close(socket) {}, // socket closed
    drain(socket) {}, // socket ready for more data
    error(socket, error) {}, // error handler
  },
});
In JSTime, a set of handlers are declared once per server instead of assigning callbacks to each socket, as with Node.js EventEmitters or the web-standard WebSocket API.
JSTime.listen({
  hostname: "localhost",
  port: 8080,
  socket: {
    open(socket) {},
    data(socket, data) {},
    drain(socket) {},
    close(socket) {},
    error(socket, error) {},
  },
});
For performance-sensitive servers, assigning listeners to each socket can cause significant garbage collector pressure and increase memory usage. By contrast, JSTime only allocates one handler function for each event and shares it among all sockets. This is a small optimization, but it adds up.
Contextual data can be attached to a socket in the open handler. 
type SocketData = { sessionId: string };

JSTime.listen<SocketData>({
  hostname: "localhost",
  port: 8080,
  socket: {
    data(socket, data) {
      socket.write(`${socket.data.sessionId}: ack`);
    },
    open(socket) {
      socket.data = { sessionId: "abcd" };
    },
  },
});
To enable TLS, pass a tls object containing key and cert fields. 
JSTime.listen({
  hostname: "localhost",
  port: 8080,
  socket: {
    data(socket, data) {},
  },
  tls: {
    // can be string, BunFile, TypedArray, Buffer, or array thereof
    key: JSTime.file("./key.pem"),
    cert: JSTime.file("./cert.pem"),
  },
});
The key and cert fields expect the contents of your TLS key and certificate. This can be a string, BunFile, TypedArray, or Buffer. 
JSTime.listen({
  // ...
  tls: {
    // BunFile
    key: JSTime.file("./key.pem"),
    // Buffer
    key: fs.readFileSync("./key.pem"),
    // string
    key: fs.readFileSync("./key.pem", "utf8"),
    // array of above
    key: [JSTime.file("./key1.pem"), JSTime.file("./key2.pem")],
  },
});
The result of JSTime.listen is a server that conforms to the TCPSocket interface. 
const server = JSTime.listen({
  /* config*/
});

// stop listening
// parameter determines whether active connections are closed
server.stop(true);

// let JSTime process exit even if server is still listening
server.unref();

​
Create a connection (JSTime.connect())

Use JSTime.connect to connect to a TCP server. Specify the server to connect to with hostname and port. TCP clients can define the same set of handlers as JSTime.listen, plus a couple client-specific handlers. 
// The client
const socket = JSTime.connect({
  hostname: "localhost",
  port: 8080,

  socket: {
    data(socket, data) {},
    open(socket) {},
    close(socket) {},
    drain(socket) {},
    error(socket, error) {},

    // client-specific handlers
    connectError(socket, error) {}, // connection failed
    end(socket) {}, // connection closed by server
    timeout(socket) {}, // connection timed out
  },
});
To require TLS, specify tls: true. 
// The client
const socket = JSTime.connect({
  // ... config
  tls: true,
});

​
Hot reloading

Both TCP servers and sockets can be hot reloaded with new handlers. 
const server = JSTime.listen({ /* config */ })

// reloads handlers for all active server-side sockets
server.reload({
  socket: {
    data(){
      // new 'data' handler
    }
  }
})

​
Buffering

Currently, TCP sockets in JSTime do not buffer data. For performance-sensitive code, it’s important to consider buffering carefully. For example, this: 
socket.write("h");
socket.write("e");
socket.write("l");
socket.write("l");
socket.write("o");
…performs significantly worse than this: 
socket.write("hello");
To simplify this for now, consider using JSTime’s ArrayBufferSink with the {stream: true} option: 
const sink = new ArrayBufferSink({ stream: true, highWaterMark: 1024 });

sink.write("h");
sink.write("e");
sink.write("l");
sink.write("l");
sink.write("o");

queueMicrotask(() => {
  var data = sink.flush();
  if (!socket.write(data)) {
    // put it back in the sink if the socket is full
    sink.write(data);
  }
});
Corking — Support for corking is planned, but in the meantime backpressure must be managed manually with the drain handler.