Scott Longberry wrote:
> Hi David,
>
> I'll chime in with the others with my congratulations! You've been
> extremely helpful and I am sure Metaweb will be glad to have you.
>
> As for opinions as to where to go with Timeline and Exhibit, I
> wouldn't mind seeing them become open source projects. I'd be happy to
> continue contributing in what small ways that I can.
>
> As for where to host the code, I do not have any practical experience,
> so I can't really offer any concrete advise here, but i would like to
> point out the obvious. Where ever the code ends up being hosted, it
> will need to be 1) extremely reliable and 2) very fast. Because
> Exhibit is hosted for all of its users, if the host goes down or
> experiences a bottleneck, everyone who uses Exhibit is affected. It
> makes me wonder if there is some way of mirroring the host and load
> sharing between the mirrors...
>
Hi Scott,
Mirrors-- that's a great idea. At least we should have 2 different API
instances, and let everybody know where they are. Authors of exhibits
must explicitly change the API URLs inside their exhibits when one API
instance fails. But at least they have some control. Right now, if
simile.mit.edu goes down, and say you're demo'ing your exhibit, there
isn't much you can do. You can't access our subversion repository, either.
Note that Exhibit has a little more than just static files. If you want
to include maps, then you need this Java servlet
http://simile.mit.edu/painter/painter
to be running to generate those map markers. You might also need
http://simile.mit.edu/babel/translator
to translate your data from some non-Exhibit native formats.
Then the follow-up question is, who will we trust to host the second API
instance? Another school? A non-commercial organization? ...
David
_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general
