# Tendermint Streaming Protocol (TMSP)
**TMSP** is a socket protocol, which means applications can be written in any programming language.
TMSP is an asynchronous streaming protocol: message responses are written back asynchronously to the platform.
*Applications must be deterministic.*
## Message types
#### AppendTx
* __Arguments__:
* `TxBytes ([]byte)`
* __Returns__:
* `RetCode (int8)`
* __Usage__:
Append and run a transaction. The transaction may or may not be final.
#### GetHash
* __Returns__:
* `RetCode (int8)`
* `Hash ([]byte)`
* __Usage__:
Return a Merkle root hash of the application state
#### Commit
* __Returns__:
* `RetCode (int8)`
* __Usage__:
Finalize all appended transactions
#### Rollback
* __Returns__:
* `RetCode (int8)`
* __Usage__:
Roll back to the last commit
#### AddListener
* __Arguments__:
* `EventKey (string)`
* __Returns__:
* `RetCode (int8)`
* __Usage__:
Add event listener callback for events with given key.
#### RemoveListener
* __Arguments__:
* `EventKey (string)`
* __Returns__:
* `RetCode (int8)`
* __Usage__:
Remove event listener callback for events with given key.
#### Flush
* __Usage__:
Flush the response queue. Applications that implement `types.Application` need not implement this message -- it's handled by the project.
#### Info
* __Returns__:
* `Data ([]string)`
* __Usage__:
Return an array of strings about the application state. Application specific.
#### SetOption
* __Arguments__:
* `Key (string)`
* `Value (string)`
* __Returns__:
* `RetCode (int8)`
* __Usage__:
Set application options. E.g. Key="mode", Value="mempool" for a mempool connection, or Key="mode", Value="consensus" for a consensus connection.
Other options are application specific.