jkroll at fas.harvard.edu
Thu Oct 30 17:22:05 EDT 2008
So it's worth noting here that 3.5 9's of uptime isn't considered good
enough for a lot of systems. . .
On Thu, Oct 30, 2008 at 5:17 PM, Jason Gao <jasongao.root at gmail.com> wrote:
> Just came across this:
> Apparently gmail has pretty high uptime. Of course, this is coming
> from google, so take it with a grain of salt. :-) I've had my fair
> share of outages.
> 2008/10/30 Joshua Kroll <jkroll at fas.harvard.edu>:
>> Or you could be really sneaky and do search on encrypted data:
>> If only pairing-based crypto were more efficient. Sigh.
>> On Thu, Oct 30, 2008 at 5:10 PM, Jason Gao <jasongao.root at gmail.com> wrote:
>>> Ah, I see your argument. I was looking at it from just the storage and
>>> retrieval angle, since the original argument that I was responding to
>>> is that Harvard could not provide 5GB of storage per user (Bruno's
>>> email). Maintenance and development would certainly be an issue, but
>>> isn't that what the FAS-IT people are for? (Well, maybe not
>>> development, but that portion could be outsourced, without significant
>>> risk or issue if an internal code review were done after delivery).
>>> On Thu, Oct 30, 2008 at 4:06 PM, Ivan Krstić
>>> <krstic at solarsail.hcs.harvard.edu> wrote:
>>>> On Oct 30, 2008, at 3:59 PM, Jason Gao wrote:
>>>>> Ivan, you're right that indexing would have to be stored locally, but
>>>>> what's wrong with storing an index separate from the content?
>>>> It's not a technical problem, it's an ownership and maintenance problem. The
>>>> appeal of S3 is not needing to set up and manage your own infrastructure.
>>>> But if you have to run a local system to deal with indexing and searches,
>>>> then you're... setting up and managing your own infrastructure.
>>>> Ivan Krstić <krstic at solarsail.hcs.harvard.edu> | http://radian.org
>>> hcs-discuss mailing list
>>> hcs-discuss at lists.hcs.harvard.edu
> hcs-discuss mailing list
> hcs-discuss at lists.hcs.harvard.edu
More information about the hcs-discuss