Joćo Campos
May 20th 04, 10:58 AM
My solution seems a bit less radical and more=20
affordable :)... I don't get any of these problems when=20
using, for example, ICQ on the machines/networks where MSN=20
Messenger is problematic. Same goes for a lot of my=20
contacts (most of which are using, like me, the high-
performant computers).
>-----Original Message-----
>Try deleting everything on yout computer without backing=20
>it up then sell your computer and go buy a new one for=20
>$28,100 on Alienware.com that should help
>>-----Original Message-----
>>MSN Messenger seems to have a very irregular behaviour=20
>>under restrictive firewalls or error-prone=20
>>networks/environments, whereas other instant messaging=20
>>protocols seem to be more stable on the same conditions.=20
>>For example, in such circunstances it is usual for MSN=20
>>Messenger to not only lose messages (ie, messages don't=20
>>get to the destination) but also not to warn the user=20
>>about this as it usually does!
>>
>>But ICQ, for example, seems to have some kind of=20
>>acknowledgement system that doesn't even allow the user=20
>to=20
>>send a new message until the previous one is received by=20
>>the other party. This can be annoying but a simpler=20
>method=20
>>could be implemented where the same kind of=20
>>acknowledgement system is used but the user can continue=20
>>to message while Messenger attempts to send the previous=20
>>messages.
>>
>>I'm aware of the fact that MSN Messenger does implement=20
>>some kind of acknowledgement system, but somehow it=20
>seems=20
>>very irregular and unsufficient. MSN Messenger should=20
>>require acknowledgement for *every* single message and=20
>if=20
>>it's not received after a certain time it should try to=20
>>send it again. After some attempts, if the=20
>acknowledgement=20
>>is not retrieved, the user should then be informed that=20
>>the message may have not reached its destination.=20
>Ideally=20
>>Messenger should also provide some kind of visual aid to=20
>>let the user know which messages are granted to have=20
>>already been received or not (like a different icon in=20
>the=20
>>beginning of the "<display name> says:" line for the=20
>>messages that have been received on the other end and=20
>>those for which the Messenger hasn't still got the=20
>>acknowledgement).
>>
>>Any help or feedback on this matter would be widely=20
>>appreciated!
>>
>>Best Regards,
>>Jo=E3o Campos
>>.
>>
>.
>
affordable :)... I don't get any of these problems when=20
using, for example, ICQ on the machines/networks where MSN=20
Messenger is problematic. Same goes for a lot of my=20
contacts (most of which are using, like me, the high-
performant computers).
>-----Original Message-----
>Try deleting everything on yout computer without backing=20
>it up then sell your computer and go buy a new one for=20
>$28,100 on Alienware.com that should help
>>-----Original Message-----
>>MSN Messenger seems to have a very irregular behaviour=20
>>under restrictive firewalls or error-prone=20
>>networks/environments, whereas other instant messaging=20
>>protocols seem to be more stable on the same conditions.=20
>>For example, in such circunstances it is usual for MSN=20
>>Messenger to not only lose messages (ie, messages don't=20
>>get to the destination) but also not to warn the user=20
>>about this as it usually does!
>>
>>But ICQ, for example, seems to have some kind of=20
>>acknowledgement system that doesn't even allow the user=20
>to=20
>>send a new message until the previous one is received by=20
>>the other party. This can be annoying but a simpler=20
>method=20
>>could be implemented where the same kind of=20
>>acknowledgement system is used but the user can continue=20
>>to message while Messenger attempts to send the previous=20
>>messages.
>>
>>I'm aware of the fact that MSN Messenger does implement=20
>>some kind of acknowledgement system, but somehow it=20
>seems=20
>>very irregular and unsufficient. MSN Messenger should=20
>>require acknowledgement for *every* single message and=20
>if=20
>>it's not received after a certain time it should try to=20
>>send it again. After some attempts, if the=20
>acknowledgement=20
>>is not retrieved, the user should then be informed that=20
>>the message may have not reached its destination.=20
>Ideally=20
>>Messenger should also provide some kind of visual aid to=20
>>let the user know which messages are granted to have=20
>>already been received or not (like a different icon in=20
>the=20
>>beginning of the "<display name> says:" line for the=20
>>messages that have been received on the other end and=20
>>those for which the Messenger hasn't still got the=20
>>acknowledgement).
>>
>>Any help or feedback on this matter would be widely=20
>>appreciated!
>>
>>Best Regards,
>>Jo=E3o Campos
>>.
>>
>.
>