[hcs-d] Webmail

Jason Gao jasongao.root at gmail.com
Thu Oct 30 17:17:24 EDT 2008


Just came across this:
http://googleblog.blogspot.com/2008/10/what-we-learned-from-1-million.html

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.

-Jason

2008/10/30 Joshua Kroll <jkroll at fas.harvard.edu>:
> Or you could be really sneaky and do search on encrypted data:
>
> http://www.springerlink.com/index/370086k273w1587t.pdf
>
> If only pairing-based crypto were more efficient. Sigh.
>
> Josh
>
> 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).
>>
>> -Jason
>>
>> 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
>> http://lists.hcs.harvard.edu/mailman/listinfo/hcs-discuss
>>
>>
>


More information about the hcs-discuss mailing list