I'm not sure why they take so long in this particular case. The 
process is just like that of HTML pages with embedded images. The 
"text" of the page is sent separately, and then the images are sent 
as they can. Usually, the system allows good interaction with the 
base info while the images are being sent. In this case the Geemail 
is essentially noninteractive until all the images have been sent -- 
and this is a bug. Perhpas Bob Arning, Mike Rueger, or Andreas can 
give us some help here.

Cheers,

Alan

-------

At 9:41 AM +0100 11/4/01, Karl Ramberg wrote:
>Alan Kay wrote:
>>
>>  John and Karl --
>>
>>  The blurry images are ones that have not yet been downloaded
>>  automatically from the server.
>Explains why they are hard to make sence of.
>
>
>>  What is the advantage of putting a Geemail in a window? -- it already
>>  has scrollbars. (You may not think so because they are very much
>>  delayed in appearing because of the slow picture download, but a
>>  mouseover the Geemail will eventually make them appear.)
>
>Why do the images take so long ? Is each image gzipped by it self
>and upploaded ? Could it speed stuff up if they got zipped in a
>archive with the relatively new archive zip tool so the
>time wasted on each part got eliminated ?
>
>Karl


--