<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi Richard,<div><br></div><div>I thought of keeping the time stamp as the key in the ets table and maintain that in state when a timeout event occurs. I hope this would help me to delete the entries in ets table with less burden.</div><div><br></div><div>Thanks,</div><div>Marutha</div><div><div><br><div><div id="SkyDrivePlaceholder"></div>> Subject: Re: [erlang-questions] Guidance to a cache mechanism<br>> From: ok@cs.otago.ac.nz<br>> Date: Wed, 31 Oct 2012 11:18:11 +1300<br>> CC: erlang-questions@erlang.org<br>> To: maruthavanan_s@hotmail.com<br>> <br>> <br>> On 31/10/2012, at 12:08 AM, Maruthavanan Subbarayan wrote:<br>> - messages contain up to 200 bytes<br>> - "maybe 500+" messages per second<br>> - maximum expiry 60 minutes<br>> for a total of 360,000,000 bytes.<br>> <br>> I'm wondering whether you actually need ETS at all.<br>> <br>> + Something gives your program a message.<br>> + Time tells your program when to delete a message.<br>> ? How is your program asked to give a message back?<br>> A message is presumably going to be requested via<br>> some sort of key, which is presumably _not_ going<br>> to be the timestamp when it arrived, so you will<br>> want some kind of index to find the right message, no?<br>> <br>> <br></div></div></div> </div></body>
</html>