aitbc
816e258d4c
Development Artifact Cleanup: ✅ BROTHER_NODE REORGANIZATION: Moved development test node to appropriate location - dev/test-nodes/brother_node/: Moved from root directory for better organization - Contains development configuration, test logs, and test chain data - No impact on production systems - purely development/testing artifact ✅ DEVELOPMENT ARTIFACTS IDENTIFIED: - Chain ID: aitbc-brother-chain (test/development chain) - Ports: 8010 (P2P) and 8011 (RPC) - different from production - Environment: .env file with test configuration - Logs: rpc.log and node.log from development testing session (March 15, 2026) ✅ ROOT DIRECTORY CLEANUP: Removed development clutter from production directory - brother_node/ moved to dev/test-nodes/brother_node/ - Root directory now contains only production-ready components - Development artifacts properly organized in dev/ subdirectory DIRECTORY STRUCTURE IMPROVEMENT: 📁 dev/test-nodes/: Development and testing node configurations 🏗️ Root Directory: Clean production structure with only essential components 🧪 Development Isolation: Test environments separated from production BENEFITS: ✅ Clean Production Directory: No development artifacts in root ✅ Better Organization: Development nodes grouped in dev/ subdirectory ✅ Clear Separation: Production vs development environments clearly distinguished ✅ Maintainability: Easier to identify and manage development components RESULT: Successfully moved brother_node development artifact to dev/test-nodes/ subdirectory, cleaning up the root directory while preserving development testing environment for future use.
80 lines
2.7 KiB
JavaScript
Executable File
80 lines
2.7 KiB
JavaScript
Executable File
"use strict";
|
|
Object.defineProperty(exports, "__esModule", { value: true });
|
|
exports.WebSocketProvider = void 0;
|
|
const ws_js_1 = require("./ws.js"); /*-browser*/
|
|
const provider_socket_js_1 = require("./provider-socket.js");
|
|
/**
|
|
* A JSON-RPC provider which is backed by a WebSocket.
|
|
*
|
|
* WebSockets are often preferred because they retain a live connection
|
|
* to a server, which permits more instant access to events.
|
|
*
|
|
* However, this incurs higher server infrasturture costs, so additional
|
|
* resources may be required to host your own WebSocket nodes and many
|
|
* third-party services charge additional fees for WebSocket endpoints.
|
|
*/
|
|
class WebSocketProvider extends provider_socket_js_1.SocketProvider {
|
|
#connect;
|
|
#websocket;
|
|
get websocket() {
|
|
if (this.#websocket == null) {
|
|
throw new Error("websocket closed");
|
|
}
|
|
return this.#websocket;
|
|
}
|
|
constructor(url, network, options) {
|
|
super(network, options);
|
|
if (typeof (url) === "string") {
|
|
this.#connect = () => { return new ws_js_1.WebSocket(url); };
|
|
this.#websocket = this.#connect();
|
|
}
|
|
else if (typeof (url) === "function") {
|
|
this.#connect = url;
|
|
this.#websocket = url();
|
|
}
|
|
else {
|
|
this.#connect = null;
|
|
this.#websocket = url;
|
|
}
|
|
this.websocket.onopen = async () => {
|
|
try {
|
|
await this._start();
|
|
this.resume();
|
|
}
|
|
catch (error) {
|
|
console.log("failed to start WebsocketProvider", error);
|
|
// @TODO: now what? Attempt reconnect?
|
|
}
|
|
};
|
|
this.websocket.onmessage = (message) => {
|
|
this._processMessage(message.data);
|
|
};
|
|
/*
|
|
this.websocket.onclose = (event) => {
|
|
// @TODO: What event.code should we reconnect on?
|
|
const reconnect = false;
|
|
if (reconnect) {
|
|
this.pause(true);
|
|
if (this.#connect) {
|
|
this.#websocket = this.#connect();
|
|
this.#websocket.onopen = ...
|
|
// @TODO: this requires the super class to rebroadcast; move it there
|
|
}
|
|
this._reconnect();
|
|
}
|
|
};
|
|
*/
|
|
}
|
|
async _write(message) {
|
|
this.websocket.send(message);
|
|
}
|
|
async destroy() {
|
|
if (this.#websocket != null) {
|
|
this.#websocket.close();
|
|
this.#websocket = null;
|
|
}
|
|
super.destroy();
|
|
}
|
|
}
|
|
exports.WebSocketProvider = WebSocketProvider;
|
|
//# sourceMappingURL=provider-websocket.js.map
|