- The client will now display all ssl errors that occur during the
handshake process properly.
- New versions of MRCI host will longer support multiple certs so
the the common name designator was removed from the client
header. It is now just 272bytes of padding reserved for future
expansion.
- Fixed the defined server header len from 35 to 37.
- The client will now respond to only reply 1 or 2 on the host
header.
- HOST_CERT was removed as a data type and the host will longer
use it.
added support for the new PROMPT_TEXT data type id. it is simply treated
like any other TEXT type for this application.
added a hiddden progress bar below the main text body that will only kick
in when it detects a string of the PROG/PROG_LAST data types.
refactored "halt" to "yield" on the client's internal command. also
refactored "text_settings" to "theme" on the json config file. the config
file name will now also include the major version number as a way to
verify compatibility as the client is updated.
changed the client's versioning system to a 2 number system. more info
about this new system was edited into the README.md file.
synced the type_id and async_id values with MRCI host.
added support for the new MRCI host 4 number versioning system. this
client will only care about the tcp_rev part of this new system for now.
any changes to the hosts' core commands shouldn't affect compatibility
with this client.
genfile commands would still not terminate properly
or would end up de-synced with the host in one way
or another.
the GEN_FILE sub-protocol has been updated to
address these issues by having the direction of the
genfile data defined in NEW_CMD so this client will
now know if the command uploads to the host or
downloads from the host when it is defined instead
of trying to determine that at runtime.
updated all documentation related to the GEN_FILE
sub-protocol to reflect these changes.
the MRCI protocol has been upgraded to support branch ids
so running multiple instances of the same command can run
at the same time at the host side. this client however
will still continue to run host commands in FIFO but this
is something that can be added in the near future.
another change to the protocol is the version negotiation
is now entirely one-sided so just the client can now
decide of the host version is acceptable or not.
the NEW_CMD frames from MRCI host will now include all of
the command documentation so listing of all available
commands and documentation is now entirely client
controlled because the host no longer have built in
documentation commands.
this client's Session object now operate in it's own
thread. for now, this does nothing but this is a prelude
for future performance updates that will including
multi-threading.
