Hi Lukasz,
I think next release is fine. this is not something super urgent.
xrdadler32 can both calculate adler32 for an ordinary file (case"a") and (b) retrieve checksum from a remote xrootd server (case "b", just like the "xrd"). So it _was_ used by both server (case "a") and client (case "b"). New xrootd server has a built-in adler32 that does exactly what xrdadler32 will do. So case "a" is no longer necessary, "b" is the only use case. That is why I propose to move it to the client rpm.
regards,
Wei Yang | [log in to unmask] | 650-926-3338(O)
On Apr 2, 2012, at 8:07 AM, Lukasz Janyst wrote:
> On Thursday, March 29, 2012 08:25:35 PM Yang, Wei wrote:
>> I have one thing to ask for help. xrdadler32 is currently in xrootd-server
>> rpm because xrootd server used to need it. Now that xrootd has a build-in
>> adler32, can this binary be moved to xrootd-client rpm?
>
> Hi Wei,
>
> sure, if you (and others) think its place is there. But I would to that for
> the next release. Is it OK with you? BTW. Why do you need it on the client
> side?
>
> Cheers,
> Lukasz
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
|