Mark,
I am having exactly the same problem, using socket.io to update status of
the switch back to the website. Communication via socket.io from the
browser to server is working fine, but for some reason I can't get the
feedback from the server working. Have you resolved your issue?
In my case I can see websocket writing back to the browser, but immediately
after that there is "transport end" message. Please see the log output
below.
info - socket.io started
debug - served static content /socket.io.js
debug - client authorized
info - handshake authorized 1517478271825090374
debug - served static content /socket.io.js
debug - setting request GET /socket.io/1/websocket/1517478271825090374
debug - set heartbeat interval for client 1517478271825090374
debug - client authorized for
debug - websocket writing 1::
new onConnect request ### my debug message
got connection from browser ### my debug message
Switch number:sw1 value:1 ### my debug message
debug - websocket writing
5:::{"name":"sw1Status","args":["{\"switch\":\"sw1\", \"value\":1}"]}
### this is message back to the browser
info - transport end
debug - set close timeout for client 1517478271825090374
debug - cleared close timeout for client 1517478271825090374
debug - cleared heartbeat interval for client 1517478271825090374
debug - discarding transport
My scripts for server and client are very similar to the examples from book
"*Programming the BeagleBone Black" by Simon Monk. *
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
