annotate src/zlib-1.2.7/examples/gzlog.h @ 83:ae30d91d2ffe

Replace these with versions built using an older toolset (so as to avoid ABI compatibilities when linking on Ubuntu 14.04 for packaging purposes)
author Chris Cannam
date Fri, 07 Feb 2020 11:51:13 +0000
parents e13257ea84a4
children
rev   line source
Chris@4 1 /* gzlog.h
Chris@4 2 Copyright (C) 2004, 2008 Mark Adler, all rights reserved
Chris@4 3 version 2.0, 25 Apr 2008
Chris@4 4
Chris@4 5 This software is provided 'as-is', without any express or implied
Chris@4 6 warranty. In no event will the author be held liable for any damages
Chris@4 7 arising from the use of this software.
Chris@4 8
Chris@4 9 Permission is granted to anyone to use this software for any purpose,
Chris@4 10 including commercial applications, and to alter it and redistribute it
Chris@4 11 freely, subject to the following restrictions:
Chris@4 12
Chris@4 13 1. The origin of this software must not be misrepresented; you must not
Chris@4 14 claim that you wrote the original software. If you use this software
Chris@4 15 in a product, an acknowledgment in the product documentation would be
Chris@4 16 appreciated but is not required.
Chris@4 17 2. Altered source versions must be plainly marked as such, and must not be
Chris@4 18 misrepresented as being the original software.
Chris@4 19 3. This notice may not be removed or altered from any source distribution.
Chris@4 20
Chris@4 21 Mark Adler madler@alumni.caltech.edu
Chris@4 22 */
Chris@4 23
Chris@4 24 /* Version History:
Chris@4 25 1.0 26 Nov 2004 First version
Chris@4 26 2.0 25 Apr 2008 Complete redesign for recovery of interrupted operations
Chris@4 27 Interface changed slightly in that now path is a prefix
Chris@4 28 Compression now occurs as needed during gzlog_write()
Chris@4 29 gzlog_write() now always leaves the log file as valid gzip
Chris@4 30 */
Chris@4 31
Chris@4 32 /*
Chris@4 33 The gzlog object allows writing short messages to a gzipped log file,
Chris@4 34 opening the log file locked for small bursts, and then closing it. The log
Chris@4 35 object works by appending stored (uncompressed) data to the gzip file until
Chris@4 36 1 MB has been accumulated. At that time, the stored data is compressed, and
Chris@4 37 replaces the uncompressed data in the file. The log file is truncated to
Chris@4 38 its new size at that time. After each write operation, the log file is a
Chris@4 39 valid gzip file that can decompressed to recover what was written.
Chris@4 40
Chris@4 41 The gzlog operations can be interupted at any point due to an application or
Chris@4 42 system crash, and the log file will be recovered the next time the log is
Chris@4 43 opened with gzlog_open().
Chris@4 44 */
Chris@4 45
Chris@4 46 #ifndef GZLOG_H
Chris@4 47 #define GZLOG_H
Chris@4 48
Chris@4 49 /* gzlog object type */
Chris@4 50 typedef void gzlog;
Chris@4 51
Chris@4 52 /* Open a gzlog object, creating the log file if it does not exist. Return
Chris@4 53 NULL on error. Note that gzlog_open() could take a while to complete if it
Chris@4 54 has to wait to verify that a lock is stale (possibly for five minutes), or
Chris@4 55 if there is significant contention with other instantiations of this object
Chris@4 56 when locking the resource. path is the prefix of the file names created by
Chris@4 57 this object. If path is "foo", then the log file will be "foo.gz", and
Chris@4 58 other auxiliary files will be created and destroyed during the process:
Chris@4 59 "foo.dict" for a compression dictionary, "foo.temp" for a temporary (next)
Chris@4 60 dictionary, "foo.add" for data being added or compressed, "foo.lock" for the
Chris@4 61 lock file, and "foo.repairs" to log recovery operations performed due to
Chris@4 62 interrupted gzlog operations. A gzlog_open() followed by a gzlog_close()
Chris@4 63 will recover a previously interrupted operation, if any. */
Chris@4 64 gzlog *gzlog_open(char *path);
Chris@4 65
Chris@4 66 /* Write to a gzlog object. Return zero on success, -1 if there is a file i/o
Chris@4 67 error on any of the gzlog files (this should not happen if gzlog_open()
Chris@4 68 succeeded, unless the device has run out of space or leftover auxiliary
Chris@4 69 files have permissions or ownership that prevent their use), -2 if there is
Chris@4 70 a memory allocation failure, or -3 if the log argument is invalid (e.g. if
Chris@4 71 it was not created by gzlog_open()). This function will write data to the
Chris@4 72 file uncompressed, until 1 MB has been accumulated, at which time that data
Chris@4 73 will be compressed. The log file will be a valid gzip file upon successful
Chris@4 74 return. */
Chris@4 75 int gzlog_write(gzlog *log, void *data, size_t len);
Chris@4 76
Chris@4 77 /* Force compression of any uncompressed data in the log. This should be used
Chris@4 78 sparingly, if at all. The main application would be when a log file will
Chris@4 79 not be appended to again. If this is used to compress frequently while
Chris@4 80 appending, it will both significantly increase the execution time and
Chris@4 81 reduce the compression ratio. The return codes are the same as for
Chris@4 82 gzlog_write(). */
Chris@4 83 int gzlog_compress(gzlog *log);
Chris@4 84
Chris@4 85 /* Close a gzlog object. Return zero on success, -3 if the log argument is
Chris@4 86 invalid. The log object is freed, and so cannot be referenced again. */
Chris@4 87 int gzlog_close(gzlog *log);
Chris@4 88
Chris@4 89 #endif