 |
 |
Hi Mikhail, Yes, the specs are fuzzy on this as we used to have an implementation in the forerunner to XRootD but it never got ported across. So, the specs remained fuzzy simply because we had no reason to flesh them out. I suppose, for now, never specify kXR_compress and your implementation should be safe. In the mean time, I will put compression elaboration on the list. Notethat cptype is a four byte field and if it’s null terminated (not clear it is – I have to look deeper) that leave only three characters for compression type. In any case, the idea was it was going to be like “lz4”. Andy From: Mikhail Ivchenko Sent: Tuesday, June 05, 2018 9:06 AM To: xrootd/xrootd Cc: Subscribed Subject: [xrootd/xrootd] specs: cpsize and cptype fields lack some documentation (#724) Specs do not clarify what's the unit of the size and how type is defined (is it the name of the compression algorithm like deflate or lz4?). As far as I got, compressed files are not commonly used in XRootD, however, I'm working on the XRootD protocol implementation in Go language and would like to clarify these details in doc string if they are available. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/724#issuecomment-394866751 ######################################################################## 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