405
406
public write(buffer: VSBuffer): void {
407
>
// If we write many logical messages (let's say 1000 messages of 100KB) during a single process tick, we do
ipc.net.ts
408
>
// this thing where we install a process.nextTick timer and group all of them together and we then issue a
409
>
// single WebSocketNodeSocket.write with a 100MB buffer.
410
>
//
411
>
// The first problem is that the actual writing to the underlying node socket will only happen after all of
412
>
// the 100MB have been deflated (due to waiting on zlib flush). The second problem is on the reading side,
413
>
// where we will get a single WebSocketNodeSocket.onData event fired when all the 100MB have arrived,
414
>
// delaying processing the 1000 received messages until all have arrived, instead of processing them as each
415
>
// one arrives.
416
>
//
417
>
// We therefore split the buffer into chunks, and issue a write for each chunk.
418
>
419
>
let start = 0;
420
>
while (start < buffer.byteLength) {
421
>
this._flowManager.writeMessage(buffer.slice(start, Math.min(start + this._maxSocketMessageLength, buffer.byteLength)), { compressed: true, opcode: 0x02 /* Binary frame */ });
422
>
start += this._maxSocketMessageLength;
423
>
}
424
>
}
425
426
private _write(buffer: VSBuffer, { compressed, opcode }: FrameOptions): void {