Replied: Wed, 27 Feb 2002 21:04:49 -0500 Replied: "John Yin" Return-Path: johnyin@anabas.com Delivery-Date: Wed Feb 27 20:58:54 2002 Return-Path: Received: from round.uits.indiana.edu (round.uits.indiana.edu [129.79.1.72]) by grids.ucs.indiana.edu (8.10.2+Sun/8.10.2) with ESMTP id g1S1ws615572 for ; Wed, 27 Feb 2002 20:58:54 -0500 (EST) Received: from epimetheus.hosting4u.net (epimetheus.hosting4u.net [209.15.2.70]) by round.uits.indiana.edu (8.12.1/8.12.1/IUPO) with SMTP id g1S1wpgx001286 for ; Wed, 27 Feb 2002 20:58:52 -0500 (EST) Received: (qmail 13073 invoked from network); 28 Feb 2002 01:58:52 -0000 Received: from capricornus.hosting4u.net (HELO anabas.com) (209.15.2.36) by mail-gate.hosting4u.net with SMTP; 28 Feb 2002 01:58:52 -0000 Received: from johnyinl ([66.47.65.114]) by anabas.com ; Wed, 27 Feb 2002 19:58:51 -0600 From: "John Yin" To: "alex ho" Cc: "Geoffrey Fox" Subject: RE: mac and slow/bad client and misleading msg Date: Wed, 27 Feb 2002 18:01:01 -0800 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0013_01C1BFB8.B7904E60" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: <001301c1bff6$cf68daa0$bc0a0a0a@alexoldlaptop> Importance: Normal X-Rcpt-To: Content-Length: 4418 This is a multi-part message in MIME format. ------=_NextPart_000_0013_01C1BFB8.B7904E60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Slow clients is mainly due to shared dispay so the obvious thing we talked about was the 1/2 resolution. As for sick clients. That is difficult......for this particular case, just disallowing Macs from joining should work. Any other case of sick clients causing problem is most likely a bug that cause the sick client to send a corrupt message. The message handling on all the clients is not robust enough to handle the corruption and then die....although that is not the case for leadingway. I think for sick clients it will have to be case by case.....no generic solution. John -----Original Message----- From: alex ho [mailto:alexho@anabas.com] Sent: Wednesday, February 27, 2002 5:26 PM To: johnyin@anabas.com Cc: alexho@anabas.com Subject: mac and slow/bad client and misleading msg john, just want to make sure that we do not support and won't be supporting Macs in th near future. we do not need to look into that for leadingway. geoffrey wants to know what could be done in case of sick/slow clients that screw up the session. can you give it some thoughts and arrange an online session for tomorrow. thanks. we can discuss removing some misleading msgs that relates to lost connections. alex ------=_NextPart_000_0013_01C1BFB8.B7904E60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Slow=20 clients is mainly due to shared dispay so the obvious thing we talked = about was=20 the 1/2 resolution.

As for=20 sick clients. That is difficult......for this particular case, = just=20 disallowing Macs from joining should work. Any other case of sick = clients=20 causing problem is most likely a bug that cause the sick client to send = a=20 corrupt message. The message handling on all the clients is not = robust=20 enough to handle the corruption and then die....although that is not the = case=20 for leadingway.

I=20 think for sick clients it will have to be case by case.....no generic=20 solution.

John

-----Original Message-----
From: alex ho=20 [mailto:alexho@anabas.com]
Sent: Wednesday, February 27, = 2002 5:26=20 PM
To: johnyin@anabas.com
Cc:=20 alexho@anabas.com
Subject: mac and slow/bad client and = misleading=20 msg

john,

just want to make sure that we do not support and = won't be=20 supporting Macs in th near future. we do not need to look into that = for=20 leadingway.

geoffrey wants to know what could be done in case = of=20 sick/slow clients that screw up the session. can you give it = some=20 thoughts and arrange an online session for tomorrow. thanks. we = can=20 discuss removing some misleading msgs that relates to lost=20 connections.

alex

------=_NextPart_000_0013_01C1BFB8.B7904E60--