On Sat, 22 Jul 2000, Peter Ajamian wrote:
No this can't be exactly it.. packets can be lost on their way, but
lost packets over a socket stream are resent, before further packets can
go through, always [packets are accepted in sequential order on both
sides and sequential order only, otherwise the connection is forfeit].
Ofcourse... high ping times and high packet losses aren't good, but
one typically doesn't attribute this to 'dropped packets', it's typically
just called 'lag'. It may be the user/server's ISP's fault or it may be a
backbone acting up -- which they've been known to do from time to time
[*BONKS Alternet* just to make sure their systems aren't starting to get
any ideas about how to be annoying again].
IMO if you increase the wait time from 15 seconds to around 60 seconds
[the default timeout for many telnet login prompts], or perhaps try 30
seconds first; you'll have far less problems with this
-Mysid
>
> Could also be dropped packets, if they are using a client that has an
> autologon feature (such as zMUD), then the client will wait forever for
> the host to send the login prompt, if that prompt does not make it to
> the client's machine then the client will wait indefinately and will
> eventually be dropped by the host for idling no matter how long the host
> is set to wait. if this is the problem then you might want to yell at
> your ISP (or something), if it happens to a lot of players then the
> problem is likely with the host's ISP, if it happens only to one or two
> players, then it is likely a problem with the ISP of those players.
>
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 04/10/01 PDT