The speed issues aren't due to the executable or language used to compile ASGS, it's due to the network latency between you and the ASGS server.Technical Wonder wrote:QUOTE (Technical Wonder @ Jan 22 2008, 10:45 AM) At the very least, a program with the same capabilities with fewer compatibility and speed issues could be written in C++.. at the very best, the ideal, if it could be (somehow) integrated into Allegiance itself now that we have the source code. The first idea, like ASGS, would actually better since ASGS can be 'decompiled' to a greater degree than something written in C++. I have no idea how the second would work, if it could work, since the source would have to be disclosed (and modified, and security features bypassed, aka a bad thing), but combining it with a small external background program which runs when allegiance runs to ensure that the executable is the proper version/size/hash, could solve that issue as well.
Almost every function of ASGS communicates with the ASGS server. If you click "exit", it sends an exit signal to the ASGS server to log you out, which then replies with a status code.
--TE
