This will provide a way to "script" Wingo to do whatever you want (I hope). The wingo-cmd program should only be a client that sends commands to Wingo over a socket.
Wingo will act as a "server" and read commands off of the socket, and then execute them. The output of those commands will then be sent back over the socket. (If there is no output, some message should still be sent to indicate success or error.)
The wingo-cmd program should also provide detail usage and a listing of all available commands.
BurntSushi
commented
12 years ago
This will provide a way to "script" Wingo to do whatever you want (I hope). The
wingo-cmdprogram should only be a client that sends commands to Wingo over a socket.Wingo will act as a "server" and read commands off of the socket, and then execute them. The output of those commands will then be sent back over the socket. (If there is no output, some message should still be sent to indicate success or error.)
The
wingo-cmdprogram should also provide detail usage and a listing of all available commands.