<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Devs,<br>
<br>
<div class="moz-cite-prefix">On 05/02/2013 12:25, Henning Westerholt
wrote:<br>
</div>
<blockquote cite="mid:10255637.sR6FZKbj4C@hwesterholt" type="cite">
<pre wrap="">Am Dienstag, 5. Februar 2013, 12:52:19 schrieb Charles Chance:
</pre>
<blockquote type="cite">
<pre wrap="">We are working on a memcached module which uses the libmemcached library, as
opposed to the (no longer under active development) libmemcache that the
existing module depends on.
Am I correct in thinking that in this instance, it would be better to create
a brand new module (with a different name) rather than modify the existing
one? In addition to changing the dependency, we will also be exporting new
commands and potentially changing the format of the exported PVs.
</pre>
</blockquote>
<pre wrap="">
Hello Charles,
as the original author of the module I'd think that changing or replacing the
existing module would be the way to go. So far I'd not recieved that much of
bug reports against the existing module. And as Alex Balashov also mentioned
recently, there are some other issues with the current library.
If existing users need to stay with the old module, its available in the git
and the existing releases, for the new release we should go with a module
which supports the newer library.
It would be nice if you could stay with the existing PV API, which I modelled
somehow after the htable module. If you need to change something, just
announce it on the devel list and ask for feedback.
Thanks and regards,
Henning Westerholt
</pre>
</blockquote>
<br>
Very happy to stay with existing PVs if possible. The only thing I'd
like to see different is to set value and expiry at the same time,
instead of having to set value, then alter expiration. This has to
be better than setting a value with some default expiry, getting
that same value back again, then re-setting the value once more with
a different expiry?<br>
<br>
Could this be implemented at PV level? Something like
$mct(key:expiry) = value? And if expiry is omitted, we use default.<br>
<br>
Regards,<br>
<br>
Charles<br>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<title></title>
<font face="Helvetica, Arial, sans-serif"><font size="2"><span
style="font-size: 10pt;"><a
href="http://www.sipcentric.com/"
title="blocked::http://www.sipcentric.com/">www.sipcentric.com</a><br>
<br>
Follow us on twitter <a
href="http://twitter.com/sipcentric"
title="blocked::http://twitter.com/sipcentric">@sipcentric</a><br>
<br>
<font color="gray"><span style="color:gray">Sipcentric Ltd.
Company registered in England & Wales no. 7365592.</span></font><br>
<font color="gray"><span style="color:gray">Registered
office: Unit 10 iBIC, <st1:place w:st="on"><st1:placename
w:st="on">Birmingham</st1:placename> <st1:placename
w:st="on">Science</st1:placename> <st1:placetype
w:st="on">Park</st1:placetype></st1:place>, <st1:address
style="BACKGROUND-POSITION: left bottom;
BACKGROUND-IMAGE: url(res://ietag.dll/#34/#1001);
BACKGROUND-REPEAT: repeat-x" tabindex="0" w:st="on"><st1:street
w:st="on">Holt Court South</st1:street>, <st1:city
w:st="on">Birmingham</st1:city> <st1:postalcode
w:st="on">B7 4EJ</st1:postalcode></st1:address>.</span></font><o:p></o:p></span></font>
<br>
<font size="3"><span style="font-size: 12.0pt"><o:p></o:p></span></font></font>
</div>
</body>
</html>