In command or RPC protocols that are written with SSH as the transport medium, is there a standard seperating character that the SSH server uses to parse commands?
For example, if we have a simple protocol defined between a client and a server, where the client will open an SSH connection to the server and then start sending bytes:
DO COMMAND <something> DO C0MMAND2
is there a standard
<something>? Or does each protocol over SSH "do it's own thing".
As an example of a standard, "Null-terminated strings are a C construct used to determine the end of a sequence of characters intended to be used as a string.": https://stackoverflow.com/questions/34621006/how-can-a-file-contain-null-bytes
If there is not a standard, are there custom parsers that need to be written for SSH servers depending on the "message format"?
My high level question is whether SSH frameworks know how to "split messages" based on some standard, or whether each SSH server for a protocol is written with a custom listener and has to know when a "full" message is received, wait for the next separating character, etc.