44 | | [ProtocolOne] provides the user two ways of executing Quagent commands. All commands are represented as objects. These objects handle writing the specified command to the server, automatically update data fields with any relevant server data response, and maintain auxiliary data related to the command, such as command [[exitcode]] and runtime. |
45 | | The user may choose to execute commands by either explicitly instantiating these objects or calling the relevant function. Each command has an object which is specific to its individual properties, such as data response, parameter access, and socket server protocol. To execute a command explicitly using the object, simply call. |
| 44 | [[ProtocolOne]] provides the user two ways of executing Quagent commands. Both of these adhere to a unique programming paradigm - one method is [http://en.wikipedia.org/wiki/Object-oriented_programming Object-Oriented] while the other is [http://en.wikipedia.org/wiki/Functional_programming Functional]. These methods are (approximately) equivalent in usability and accessibility, so the user may choose to use whichever paradigm is preferred. |
| 45 | The user may choose to execute commands by either explicitly instantiating the command objects or calling a relevant function. Internally, all commands are represented as command-specific objects. These objects handle writing the specified command to the server, automatically update data fields with any relevant server data response, and maintain auxiliary data related to the command, such as command [[exitcode]] and runtime. To execute a command explicitly using the object, simply call the member function {{{run()}}}. Function calls automatically instantiate, run, and return the relevant object. |