Shoutbox

quote:

---

Originally posted by dttvb
?!?
Tabbed convos???

---

A feature in Plus!, it groups the conversations together to form one window, therefore yo uwont need to close the windows to keep your desktop clutter free (this is an alternative though)

Ok!

quote:

---

Originally posted by zaidgs
Cookie is saying that if a conversation is never ended, then it is always open, which will cause heavy load on the network, so i agree that 'impractical' is a better way to describe the situation, and i believe he actually meant it tht way, so dont pick on the very exact word he is using, cuz from the context it is so obvious that he knows what he's talkin about.

---

I tell you again, the MSNP automatically closes inactive sessions after X time.  That's why or how SPNG detects you are timed out or left, unless you make a plugin that sends OUT with a special number  (can't remember), then it'll make it think you timed out.. hmm..

quote:

---

Originally posted by brian

I tell you again, the MSNP automatically closes inactive sessions after X time.  That's why or how SPNG detects you are timed out or left, unless you make a plugin that sends OUT with a special number  (can't remember), then it'll make it think you timed out.. hmm..

---

Exactly what i was going to say, all these ideas of "hiding the window to keep the connection going" will not work as the MSN Messenger servers will automatically close your connection even if you leave your contact's window open after a predetermined time of inactivity.

This is in place to save more precious bandwidth and unneccessary load on the MSN Messenger servers. Because of this automated closing of the connection by the servers StuffPlugNG will occasionally report to the user that you have "closed the window" even though you actually haven't - rather the MSN Messenger servers have closed your connection due to inactivity.

Just to point out, Chestah, It tells you the conversation has timed out (SPNG).

quote:

---

Originally posted by brian
Just to point out, Chestah, It tells you the conversation has timed out (SPNG).

---

True, but sometimes it also incorrectly notifys the user that their contact has "opened" or "closed" their window. This was the reason why this feature was removed from SPNG. The only reason it was brought back was because of the constant threads and requests of people to bring it back even though it was made quite clear that it is not 100% accurate.

Mike! you are the man!!!

excelent job, oh man with few piano lessons!

thanks go out to thoes who took action.
this is most apreciated upon levels of time spent for this problem.

******************************

and to all thoes who spent their life moments making this thread off-topic and hell, welp, i know you are prolly doing it to other people this very moment, so.. i hope one day you look back on your life and realize the nothing you acomplished.

*gives a flick of his tail and bounces off happily*

What happens to the other person who doesn't use this program?

He/she will get the OUT message, close the connection for you. Am I right?

quote:

---

Originally posted by linx05
What happens to the other person who doesn't use this program?

He/she will get the OUT message, close the connection for you. Am I right?

---

Actually, I don't think so, because, the filter I made blocks the OUT messages from being sent, so the other contact, never receives the OUT message...

However, I think that there is a big problem...
I turned this filter on, and then went to BOT2K3's tribunal game.
I left the conversation, and BOT2K3 messaged me again with the other message that was received.
That was actually normal, because BOT2K3 did not receive the OUT message.
But then, it seemed that BOT2K3 did not receive any of my messages...
I think that it was because, msn thought that it sent the OUT message, so when BOT2K3 talked to me, msn tried to establish a new connection, but it couldn't because, there was another connection established.
So, msn was trying to send the message, but it couldn't because it didn't found an established connection (it actually thought that it closed the other one...), so, the message couldn't be sent...

I dont know if the filter caused this, or it just happened then, but you better check it out

what if the OUT message wasnt just blocked? maybe there is a following data packet specifying what kind of OUT it is.

the 'minimized window for 2 days' senario keeps me thinking.
maybe the MSN servers send a 'timeout' message to both clients, and after reciept, even though your window is minimized, a new connection is established seamlessly.

so.. since this setup, doesnt seem to quite work, or in any real way fixable, how about we do the reverse, and after every message sent, send an OUT message right after.

this way your contact would be inclined to disable that feature.

anyhoo, just a thought. remember to stay outside of the box

---

oh, just another thought.
maybe after each killed OUT message, you have an app send an 'IN' message back to MSN, doing kindof like a fake connection reistablish.
but it would use the same ports, and remember which TCP packet number was used last.

i was thinking that MSN might need actual typed data, before it opens a window. so that doing this wouldnt cause a loop, close the window, auto pops back open.