Replied: Thu, 15 Aug 2002 06:48:56 -0500 Replied: "alex ho" Return-Path: alexho@anabas.com Delivery-Date: Thu Aug 15 02:40:48 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 g7F7emm15789 for ; Thu, 15 Aug 2002 02:40:48 -0500 (EST) Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by round.uits.indiana.edu (8.12.1/8.12.1/IUPO) with ESMTP id g7F7hfDB009353 for ; Thu, 15 Aug 2002 02:43:41 -0500 (EST) Received: from user-105nddl.dialup.mindspring.com ([64.91.181.181] helo=alexoldlaptop) by gull.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 17fFIC-0002r3-00; Thu, 15 Aug 2002 00:43:40 -0700 Message-ID: <000a01c2442f$0ffebe60$bc0a0a0a@alexoldlaptop> Reply-To: "alex ho" From: "alex ho" To: "John Yin" , "Geoffrey Fox" Cc: "Xu Geng" , "alex ho" Subject: Becom Software Date: Thu, 15 Aug 2002 00:40:43 -0700 Organization: Anabas, Inc. MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C243F4.630A5D20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Content-Length: 2336 This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C243F4.630A5D20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I am just done with the conference call with Becom. Very glad to find = out that they are serious about working with us. They are setting up a = Linux server at this time. =20 The plan is that after testing and assume successfully as it should be, = they plan to have a "seamless integration" of their elearning product = with ours. In their words, they said "perfect integration". In the mean time, I will prepare a modified whitepaper to address their = description of actual infrastructure which they said some broadband and = some narrowband. They intend to use ours on broadband. Our server = adaptor architecture could handle bandwidth variability gracefully when = done but for now, I need to say so in a whitepaper. ------=_NextPart_000_0007_01C243F4.630A5D20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I am just done with the conference call with = Becom.  Very=20 glad to find out that they are serious about working with us.  They = are=20 setting up a Linux server at this time. 
 
The plan is that after testing and assume = successfully as it=20 should be, they plan to have a "seamless integration" of their = elearning=20 product with ours. In their words, they said "perfect = integration".
 
In the mean time, I will prepare a modified = whitepaper to=20 address their description of actual infrastructure which they said some=20 broadband and some narrowband.  They intend to use ours on = broadband. =20 Our server adaptor architecture could handle bandwidth variability = gracefully=20 when done but for now, I need to say so in a=20 whitepaper.
------=_NextPart_000_0007_01C243F4.630A5D20--