Hi Eric,

In my humble opinion, you are *far* better off hosting the libraries yourself 
rather than depending on an .mit.edu server.
Like, night and day better off.

The Yahoo folks have studied the issues of people's caches being primed and the 
effect is, unfortunately, much less than what would be hoped for.
The odds of one of your clients having a cached version of the Simile libraries 
from some other Simile-based page that is not connected to your app are tiny. 
Or smaller.

Be vertically integrated, host it yourself.

Regards,

Larry





________________________________
From: Eric Pugh <[email protected]>
To: [email protected]
Sent: Friday, December 19, 2008 8:52:19 AM
Subject: Re: simile.mit.edu down?


Joern,

We are seeing the same thing.  I had made the assumption that this  
site would be more reliable then hosting it ourselves, and allow the  
possiblity that folks might already have the javascript cached  
locally, however, maybe we are better off hosting it ourselves :-(

I know Google had an effort to host some big javascript libraries, is  
there anything like that for the Simile assets?

Eric


On Dec 19, 2008, at 4:25 AM, Jörn Clausen wrote:

>
> Hi!
>
> I think simile.mit.edu is down. The site is not reachable, and so are
> sites still using the code hosted there.
>
> Is this a planned downtime? Did I miss the EOL announcement??
>
> -- 
> Joern Clausen
> [email protected]
> http://www.oe-files.de/oefiles/
> http://thebloeg.blogspot.com/
>
> >

-----------------------------------------------------
Eric Pugh | Principal | OpenSource Connections, LLC | 434.466.1467 | 
http://www.opensourceconnections.com





--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"SIMILE Widgets" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/simile-widgets?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to