Re: rs_mdfour functions and librsync >= 0.9.6
"Shirish H. Phatak" <[email protected]> Wed, 07 Apr 2004 23:11:03 -0400
| Newsgroups | gmane.network.librsync.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --------------020409020204050203000003 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Martin Pool wrote: >On 7 Apr 2004 Shirish Hemant Phatak <[email protected]> wrote: > > > >> Hmmm...I suppose if this is going to require an API change anyway >>and it is not widely used, you may as well drop it. I would defnitely >>recomend adding a whole file checksum though. >> >> > >I think the 0.9 librsync.h exposed some internal functions that were >kind of useful, but perhaps didn't really need to be exposed. md4 >kind of fell right on the crack. > > Yes. I first noticed it when I started looking at upgrading the LibRSync perl module. Then I realized my C code was using it too. But moving to libmd is easy enough. >> Incidently, what would you suggest using instead of the librsync md4 >>apis for Windows? Does libmd work there as well? There are probably >>better options, I guess it's time to take a look. >> >> > >I would think any problems on Windows would be just incidental, since >it is very plain C. > > Yup...seems to work just fine! Thanks... Shirish --------------020409020204050203000003 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"> <title></title> </head> <body text="#000000" bgcolor="#ffffff"> Martin Pool wrote:<br> <blockquote type="cite" cite="[email protected]"> <pre wrap="">On 7 Apr 2004 Shirish Hemant Phatak <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a> wrote: </pre> <blockquote type="cite"> <pre wrap=""> Hmmm...I suppose if this is going to require an API change anyway and it is not widely used, you may as well drop it. I would defnitely recomend adding a whole file checksum though. </pre> </blockquote> <pre wrap=""><!----> I think the 0.9 librsync.h exposed some internal functions that were kind of useful, but perhaps didn't really need to be exposed. md4 kind of fell right on the crack. </pre> </blockquote> Yes. I first noticed it when I started looking at upgrading the LibRSync perl module. Then I realized my C code was using it too. But moving to libmd is easy enough.<br> <blockquote type="cite" cite="[email protected]"> <pre wrap=""></pre> <blockquote type="cite"> <pre wrap=""> Incidently, what would you suggest using instead of the librsync md4 apis for Windows? Does libmd work there as well? There are probably better options, I guess it's time to take a look. </pre> </blockquote> <pre wrap=""><!----> I would think any problems on Windows would be just incidental, since it is very plain C. </pre> </blockquote> Yup...seems to work just fine!<br> <br> Thanks...<br> <br> Shirish<br> </body> </html> --------------020409020204050203000003-- ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click