29 results found
-
Web Sockets: can you publish the "version" of the WebSocket support on your docs pages?
Then we can tie the Spectacles IK version to the WebSocket support, or how ever it happens. It is a bit tricky inside of a project to figure out if the upgrade to a module is applied properly.
1 vote0 comments · Snap OS / System UI: (Voice commands, hand tracking, Lens Explorer, notifications, connectivity) · Admin → -
Web Sockets: publish your test results against a known conformance suite
The known test suite is autobahn : https://github.com/crossbario/autobahn-testsuite (be careful ... this repo links to at least one company that no longer exists and it is NSFW). Conformance results would help . Since the suite has been ported into python, C++ (boost), etc., you can pick the best and most current implementation.
1 vote0 comments · Snap OS / System UI: (Voice commands, hand tracking, Lens Explorer, notifications, connectivity) · Admin → -
Web Sockets: better error handling in WebSocketErrorEvent
an event is nice, an event with the error message encoded would be more useful because websockets are tricky to debug without full control of the end to end set up
1 vote0 comments · Snap OS / System UI: (Voice commands, hand tracking, Lens Explorer, notifications, connectivity) · Admin → -
Web Sockets: support for ws://
support for ws:// for self hosting/local hosting, it is easier to use and test for "non-public" use to let us decide for ourselves if we want to . ** Does this work? **. I realize setting up the trust and security is sort of inherent in web infrastructure, and I was not able to make this work with any servers I tested with. It would be great to document the end to end setup if there is one that is known to work.
1 vote0 comments · Snap OS / System UI: (Voice commands, hand tracking, Lens Explorer, notifications, connectivity) · Admin → -
Web Sockets: WebSocket.binaryType = 'arraybuffer' is unsupported
WebSocket.binaryType = 'arraybuffer' is unsupported
1 vote0 comments · Snap OS / System UI: (Voice commands, hand tracking, Lens Explorer, notifications, connectivity) · Admin → -
Web Sockets: reateWebSocket factory method is missing an argument for setting the protocol
The createWebSocket factory method is missing an argument for setting the protocol. See: The new WebSocket(url, protocols) constructor steps are: .... all of the other websocket apis out there allow this protocol field. Typically, a server will implement a call like request.accept('echo-protocol') or something like 'sec-websocket-protocol'. Real browsers send their request origin along. This limitation in the current design may actually crash servers on connection if the server hasn't set it self up to have some defensive design. I have test cases where my spectacles can crash the server because it passes no protocols.
1 vote0 comments · Snap OS / System UI: (Voice commands, hand tracking, Lens Explorer, notifications, connectivity) · Admin → -
Web Sockets: API parity with W3C or IETF or WhatWG
https://websockets.spec.whatwg.org/#the-websocket-interface . It seems mostly conforming but there are a few differences.
1 vote0 comments · Snap OS / System UI: (Voice commands, hand tracking, Lens Explorer, notifications, connectivity) · Admin → -
Web Assembly (WASM) support
Just wanted to put it out there that wasm module support in Specs lenses would be awesome. Specifically I want to be able to run things like retro game emulators or other emscripten compiled things within a lens with decent performance.
1 vote0 comments · Snap OS / System UI: (Voice commands, hand tracking, Lens Explorer, notifications, connectivity) · Admin → -
Component not yet awake error is too vague
One of the more annoying errors is "Component not yet awake". Can we please get a script name and line where that happens?
1 vote0 comments · Lens Studio Integration: (Deploying to device, debugging tools, simulation, API limitations) · Admin →
- Don't see your idea?