Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
thinkgear_connector_development_guide [2014/06/24 14:31] neurosky |
thinkgear_connector_development_guide [2014/07/01 12:09] neurosky [Introduction] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== ThinkGear Connector Development Guide ====== | + | ## ThinkGear Connector Development Guide ## |
| ====== Introduction ====== | ====== Introduction ====== | ||
| The ThinkGear Connector (TGC) is an executable that provides a daemon-like service that manages communications with ThinkGear devices, such as the MindWave and MindWave Mobile, that are connected to the computer. The TGC runs continuously in the background, and keeps an open socket on the local user's computer, allowing applications to connect to it and receive information from the connected ThinkGear devices. This means that any application in any language that can open and read from sockets (such as Flash's ActionScript3 and other scripting languages) can connect and receive data from a headset. | The ThinkGear Connector (TGC) is an executable that provides a daemon-like service that manages communications with ThinkGear devices, such as the MindWave and MindWave Mobile, that are connected to the computer. The TGC runs continuously in the background, and keeps an open socket on the local user's computer, allowing applications to connect to it and receive information from the connected ThinkGear devices. This means that any application in any language that can open and read from sockets (such as Flash's ActionScript3 and other scripting languages) can connect and receive data from a headset. | ||
| <important> | <important> | ||
| - | The following is outdated. TGC does implement the ThinkGear Socket Protocol. | + | This update indicates that TGC implements the ThinkGear Socket Protocol. |
| - | + | ||
| - | TGC does **//not yet completely implement the ThinkGear Socket Protocol//** specification, specifically the authorization components. Any authorization commands sent to TGC will simply be **ignored**; applications designed for TGC should not expect any response from the authorization commands. | + | |
| </important> | </important> | ||