disconnect after some time about elephant.io HOT 7 CLOSED

Hi @bazo

Thanks for using Elephant.io !

We developed Elephant to emit in some of our cron jobs some events. It was not designed to have a persistent connexion in mind. Socket.io has a powerful deconnect / reconnect mechanism implemented (server side AND client side)

We did not re-implemented this, because it was in our opinion not very relevant to persist a connexion in PHP.

What we do is:

connect
authenticate
emit message
disconnect

Why don't you do the same, on some relevant percents, connect and send the progess status ?

from elephant.io.

currently i have it like that, because it;s the only way it works.

the problem is it makes the whole process slower,for example an import that took around 0s takes 6s, 40s take 70s, 700s take 750s and so on, all because of opening and closing connections.

i have implemented a workaround that keeps the connection open if the amount of items to import is lower than some number, otherwise it always opens a new connection, emits then closes.

would it be hard to implement the events like socket.io has by myself?

from elephant.io.

Maybe that's a silly question, I'm sorry about that, but if you're displaying the progress percentage on the browser, why don't you use the Socket.IO client, which manages persistent connection, reconnection, and so on ?

from elephant.io.

i use the sockiet.io client, but that can't be used from php, right? i just think it is a waste of requests, bandwith or other resources, if you need to connect, emit, disconnect every time. if it can be prevented why not do it?

from elephant.io.

What is in your php.ini configuration file your php script execution timeout ?

I think keeping open the connexion is keeping open a php thread (how is it not blocking with your import ?), and that php thread has a max exec time no ?

from elephant.io.

it's run from cli so there's no time limit. the thread is already started by the import, the client doesn't start any new threads.

the client itself is still sending data as if it were connected. i just see a message in socket.io debug that it was disconnected. maybe it's some socket setting that resets the connection and the client doesn't react to that

from elephant.io.

As it's been a while and the code has been rewritten from scratch, closing this issue

from elephant.io.