Under what circumstances do all Handlers get flushed? about strophejs

[isfarax]

what do you mean by this?

usually i would destroy the variable that holds the handler and then when you disconnect you also have to flush in the process too - and thats what people on the internet do anyway.

i think that way you can manage what you do with the handler in each case.

[akarelas]

Are we talking about the same kind of handlers here? I'm talking about the kind of handlers that you create with connection.addHandler(...)

So, how do you suggest I "destroy the variable that holds the handler"? How do I destroy a variable? Also, you say I should flush in the process. Which process are you talking about? How do I flush it?

Thanks.

[akarelas]

Is anyone around?

[isfarax]

Sorry I forgot to reply, the flush method is within the strophe connection i believe. i will have to sift through my code later and get back to you. hang tight my friend.

[akarelas]

Hi @isfarax , do we have any news? The flush method does something completely different, it flushes the data, so it's not what I want.

[isfarax]

Hi @akarelas

this is from the book:

var ref = conn.addHandler(my_handler_function, null, “message”);
// once the handler is no longer needed:
connection.deleteHandler(ref);

that is how you should add and remove references to a handler. i hope this is what you are wanting to achieve.

[akarelas]

This doesn't work. I tried it on my websocket-style connection. If you don't believe me, that deleteHandler does absolutely nothing, tell me and I will demonstrate it with a plunkr

[isfarax]

if you are wanting to manage user/connection session, you should look into RID and SID because if the connection gets disconnected then i wouldnt be surprised if the handlers get wiped out too.

[akarelas]

What's RID and SID?

[akarelas]

All I want is to not end up with 150 thousand handlers on my connection, just because the server was down for a minute and my client was trying to reconnect again and again.

[akarelas]

Would you like me to set up a plunkr, to demonstrate to you that deleteHandler does absolutely NOTHING?

[akarelas]

Will you do something about it afterwards, when I've shown it?

[isfarax]

SID (Session Identification) and RID (Reference Identification) are to manage user sessions, typically when a user is attempting to login in again. after you disconnected, you can use the SID and RID to login into the server, it is like taking a shortcut and it is the recommending way of doing it - this also doesnt create 150 thousand connections to your server.

[akarelas]

Does this mean you're not interested in my demonstrating that deleteHandler does nothing?

[isfarax]

i am, show me

[Gordin]

@akarelas

1. This works, the deleteHandler function does not do nothing...
   var ref = conn.addHandler(my_handler_function, null, “message”);
   // once the handler is no longer needed:
   connection.deleteHandler(ref);
   If you can show us how to reproduce that it doesn't it will be fixed.
2. The handlers are always flushed after a disconnect and during a reset. Specifically a few lines after the Strophe.Connection Status is set to DISCONNECTED. The only way handlers from a previous session could interfere with a new one would be if you would hook status DISCONNECTING or DISCONNECTED or instantly reconnect before the handlers are cleared. Depending on your hooks for DISCONNECTING or DISCONNECTED the handlers could survive a reconnect for a few seconds.

I'm not really sure why the handlers are currently cleared after DISCONNECTED is set, I'll push a patch that reverses the order here. If you still have problems reopen this.