#11401: Lightstreamer regression in web+ ----------------------------------------+---------------------------- Reporter: AlienSoldier | Owner: pulkomandy Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/WebPositive | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 0 | Platform: All ----------------------------------------+---------------------------- Comment (by AlienSoldier): I contacted the developpers here is what they have to say: " I confirm that if the websocket does not work the Lightstreamer JavaScript client library should automatically fall back to other technologies. It may be that the implementation of websocket of Haiku behaves in a completely unexpected way so that the algorithm can not fall back to the HTTP-Streaming or HTTP-polling. If you have the possibility to act on the client code you should try to force a transport defferent from WebSocket, see here http://www.google.com/url?q=http%3A%2F%2Fwww.lightstreamer.com%2Fdocs%2Fclient_javascript_uni_api%2FConnectionOptions.html%23setForcedTransport&sa=D&sntz=1&usg=AFQjCNFte8ZVx2lQkRbJkjGyCqgjBq0EZg . In your case should be fine something like this: ConnectionOptions.setForcedTransport("HTTP"); Otherwise, you'd be able to disable websocket browser-side? (Something like the network.websocket.enabled flag in firefox) " Perhaps it does not fall back now that the socket implentation is more advanced so it stay in limbo? If so and not really usable perhaps it would be better to revert it until more compliant (unless it can be usefull for some site in the current state). -- Ticket URL: <https://dev.haiku-os.org/ticket/11401#comment:2> Haiku <https://dev.haiku-os.org> Haiku - the operating system.