The Leap Motion service is an application running as a daemon on Unix-style platforms (Mac OS X and Linux) and as a service on Windows. Its job is to communicate with the controller hardware devices over USB, post-process frames of hand- and scene-tracking information, and then make this data available to API clients in their native formats. When we use the C++ API to create our frame data Listener
, it is really communicating with the Leap Motion service behind the scenes, which is why the service must already be started by the user for our Listener
to receive any updates. In the case of our client-side JavaScript code, the frame data is transmitted over a socket, although the details of that communication are still hidden by the consumer of the Leap API.
You're reading from Leap Motion Development Essentials
The rest of the page is locked
You have been reading a chapter from
Leap Motion Development EssentialsPublished in: Oct 2013Publisher: PacktISBN-13: 9781849697729
© 2013 Packt Publishing Limited All Rights Reserved