Chrome App Support

[aaronfrost]

The TCP socket connection made by Chrome apps doesn't connect to the EyeTribe Server successfully. I have tried both a WebSocket connection (using a simple page) and using the Chrome API, chrome.sockets.tcp, by way of creating a chrome app, requesting permission for socket access, and using the API to create and then connect the socket to 127.0.0.1:6555. Neither work.

When I create the WebSocket, and point it at 127.0.0.1:6555, the lights on the EyeTribe turn on, like something is about to happen, but the WebSocket never successfully establishes a connection with the Server.

When I create a chrome.sockets.tcp socket and connect to 127.0.0.1:6555, I get different results. I can create and connect the the socket. I can then send a message but nothing happens.

I am not sure what to do to get this to work in Chromeapps. But it appears to be close. Is it possible that you might work with me to get the code to work?

[Martin]

Hi Aaron,

The lights will come on once a client connects to the server and will be kept on as long as a client is active (e.g. sending heartbeats). Haven't attempted Websockets myself but know that it requires a upgrade handshake which is currently is not supported by the TET Server.

Some time ago the user nulltask posted code that will create a websocket bridge to the server. Think it was working alright on Windows 8.

We have native support for Websockets in the server on the road-map, it would make it so much easier to do pure javascript+json development. I cannot be specific on when this feature will appear.

[warbyrd]

Hi, is there no news to this problem? It's been a year now

[Martin]

Its a feature request, not a problem.

No official support yet but check out this:
eyetribe-websocket