*test failures
I have another question for you guys. How would I go about testing my client implementation of sockjs? I've been able to get my client up and running with a socket connection, and my logic seems to be functional. But, of course, I'd like to unit test the onopen, onmessage, and onclose functions. How can I mock a server emitting a socket message to my client and test my response logic? I'm using Angular and Karma/chai if that helps.
So you can have a simple mock object that calls onopen, onmessage, and onclose as part of your tests
Never mind; just remembered this library attempts to really follow the spec :)
Is there a way to print out low-level websocket data from sockjs? Or a good way to sniff the raw network connection? I haven't had success with either approach yet, and would love some help.
Ah, problem seems to be solved. I found the place to insert a print statement by triggering a crash from within my .on('data', ..) handler and looking at the stack trace. I added a print statement to the first call that came after node's internal junk, which was in faye's websocket driver, and found that the network frame was reaching the physical interface but was not actually getting to faye. This meant that the bug was either in the OS or in node.
I tried upgrading node to v4 (I was at v.10) and the bug went away. So the solution was to upgrade node. Apparently there are bugs with old versions of node when running semi-heavy websockets traffic.
I want to close the server if there are no connections anymore. Is this possible?
naive attempt would be to count
on('connection') and conncetion.close, but this seems fragile to me
??
I think problem with between Firefox and SockJs
Hi guys, I’m using sockjs with Primus. Once the connection is established, I want to insert/update a database record, once that’s done I’d like to start handling the messages so I’d know which user based on my DB record sent the message. The problem is that if I wait for the database queries to finish I will miss the initial messages from the client since binding the
data event only happens afterwards. If I bind the data event first, I will not know which client sent the message. What’s the logical way to approach this?
I could probably bind the event and before I know the client, store the messages in an array and after the database work is done, take the messages from the array and reassign them to the client.
messages will also be stored in a database
Hi guys. Could you please assist with the question? http://stackoverflow.com/questions/41394049/does-it-make-sense-to-create-promise-from-stompclient-send-request
Uncaught failure in sockjs request. Websocket handshake failure.nested exception is java.lang.illegalargumentexception: No 'javax.websocket.server.servercontainer' servlet context attribute. Are you running in a servlet container that supports JSR-356
We are trying to use SockJS with StompJS . Our site runs wicked slow and I notice my connection seems to go through all the fallback protocols at about 15s intervals... is there anyway to up the fallback delay? I'm just trying to eliminate this as a possible issue.
at the same time it looks like it tried to fall to xhr_streaming then iframe then htmlfile and then jsonp and then it just dies for good. "Whoops! Lost connection to..."
even while it's dead it's still responding to heartbeats.... but it's just not actually working
any ideas?
xhr doesn't seem to work at all either... is there some spring configuration magic I missed for this?
Searching in the repository, there's a Options parameter in the constructor, but there's not an option to set the Access-Control-Allow-Origin :-/