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.
along with the main thread, the project now supports 3
additional threads.
-the Session object operates in it's own thread that
will take data directly from the host, process and
direct it to various parts of the client.
-the main GUI and client command objects will continue
to operate on the main thread.
-the GenFile object which is dedicated to processing
GEN_FILE data to or from the host will operate in
it's own thread.
-last thread is for a new object called TextWorker.
this object will take all of the text buffered from
all of other objects and then send the text to be
displayed by the main GUI in a slower, controlled
manner.
by building out all of these threads, the main GUI
will not lag even when the host or the client itself
is outputting an excessive amount of data.
fixed a bug that prevented the client from being able
to totally unhook a genfile command of it crashes.
also reduced the default max lines from 5000 to 1000.
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.
