How to keep connection open? about oboe.js

[ooxi]

The question is why does your server drop the connection after 120 seconds of inactivity? Browsers do not normally act this way if you start sending at least some data (for example the { if you intend to send an object).

[jimhigson]

Yeah, like @ooxi says, I'm not seeing why the server would shut the connection if not data is being sent down it.

If the server is closing the connection, because Oboe is a client-side library so there's not much it can do to influence the behaviour on the server.

The only client side answer I can think of is to have the client re-open the connection when it goes down. You'd probably lose messages sent in the meantime though.

If you want to filter out fake data, you could always tag 'real' data with an attribute and then detect it like: oboe(url).node('!.{notfake}', function(realData){})

[JuanCaicedo]

@goloroden What languages/frameworks are you using on your server-side? I would encourage you to ask the question there since as @jimhigson mentioned, this is out of Oboe's control. Would love to help though!

[goloroden]

We are using Node.js on the server.

[JuanCaicedo]

@goloroden I think you might be able to achieve this using the keep-alive http header. You could pass it with oboe like this

oboe({
    url: 'http://localhost:3000/data',
    headers: {
      'Connection' : 'keep-alive'
    }
  })

You need to teach your node server how to handle that header though since it seems like there's no official spec for it. I haven't tried it, but you could try using the agentkeepalive module.

Hopefully that works, I would be interested to find out how it goes!