JSON RPC using TCP, with a separator NULL character

[sbendt]

I have an implementation, where the communication protocol is based on JSON RPC. The implementation is a little different, since there is a "separator character" (0x00/NULL) between the messages being received and transmitted.

Is it possible to extend the existing JSON RPC TCP implementation to parse/ignore the separator char when receiving and inject it after transmitting messages?

[pocesar]

@sbendt not without a code change. the event emitters (Socket / Net) aren't exposed, so you can't use a Transform stream to pipe the answer, cork the stream until you see a null character, then uncork it.

[sbendt]

@pocesar thank you for the prompt reply. Ill consider writing a one-off for this, or maybe fork your repo - if that is okay?

[pocesar]

@sbendt sure, be my guest 😃