7 * The <<conf:,configuration file parser>> has been improved:
8 ** *Incompatible:* The interface of the <<heap:,heap>> module was cleaned up
9 to remove non-systematic side-effects. The `HEAP_INSERT` operation is now
10 a proper insert (previously, it was just cleanup after insertion performed
11 by the caller), similarly `HEAP_INCREASE` and `HEAP_DECREASE`. The `HEAP_DELMIN`
12 operation was renamed to `HEAP_DELETE_MIN`. New operations `HEAP_REPLACE` and
13 `HEAP_REPLACE_MIN` have been added. If you need to track positions of elements
14 in the heap, please check the notes at individual functions.
15 ** Multiple instances of the configuration parser are supported.
16 ** *Incompatible:* As there may be more instances, we can no longer use
17 global variables to control the configuration system. In particular,
18 `cf_need_journal` and `cf_pool` variables have been replaced by
19 functions <<conf:fun_cf_set_journalling,`cf_set_journalling()`>> and
20 <<conf:fun_cf_get_pool,`cf_get_pool()`>>.
21 ** *Incompatible:* Loading of configuration files has been decoupled from
22 the getopt wrapper, so you might need to include `conf.h` for functions
23 which were previously declared in `getopt.h`.
24 ** New functions have been added:
25 <<conf:fun_cf_open_group,`cf_open_group()`>>,
26 <<conf:fun_cf_close_group,`cf_close_group()`>>, and
27 <<conf:fun_cf_revert,`cf_revert()`>>.
28 * <<daemon:,Daemon helpers>> have been added including a new `daemon-control`
29 utility. The old `daemon-helper` utility has been obsoleted and it is not
31 * <<signal:,Signal helpers>> for translation between signal names and numbers
33 * The fastbuf I/O layer received a new back-end <<fastbuf:fbmulti,fb_multi>>,
34 which concatenates several fastbuf streams to form a single virtual stream.
39 * *Incompatible:* The `timestamp_t` type has been decoupled from wall clock time.
40 It now specifies the number of milliseconds from an unspecified origin, so that
41 it can for example refer to the system monotonic clock. The `ucw_time_t` type
44 * The <<mainloop:,mainloop>> module has been rewritten:
45 ** Multiple instances of the main loop are supported (to be used in different
46 threads or locally within a library function).
47 ** The new implementation is more efficient: it uses heaps for timers,
48 epoll() for file descriptors (when available).
49 ** The return value of <<mainloop:struct_main_file,`main_file`>> handlers has been
50 changed to <<mainloop:enum_main_hook_return,`HOOK_IDLE`>> and <<mainloop:enum_main_hook_return,`HOOK_RETRY`>>.
51 However, the numerical values are equal, so old code should keep working.
52 ** *Incompatible:* The main loop time (`main_now`) has been decoupled from wall clock time
53 and moved to a field in the `main_context` structure. It can be accessed either directly
54 or via <<mainloop:fun_main_get_now,`main_get_now()`>>. The `main_now_seconds` variable has
55 been removed, `main_idle_time` has become a structure field.
56 ** *Incompatible:* The interface for asynchronous reading and writing
57 (file_read() and friends) has been separated from the core of the main loop.
58 Use <<mainloop:struct_main_block_io,`struct main_block_io`>> and related functions instead.
59 ** *Incompatible:* file_close_all() is gone. You have to call <<mainloop:fun_main_teardown,`main_teardown()`>>
60 or <<mainloop:fun_main_destroy,`main_destroy()`>> to clean up properly after fork().
61 ** Added support for <<mainloop:signal,synchronous delivery of signals>>.
62 ** Added relative timers: <<mainloop:fun_timer_add_rel,`timer_add_rel()`>>.
63 ** Modification of events from a running event handler is always safe.
64 ** Deleting an already deleted event is always safe.
65 ** For any event type, it is possible to ask whether it is active (added to the mainloop) or not: <<mainloop:fun_hook_is_active,`hook_is_active()`>> and friends.
66 ** A new mainloop front-end for asynchronous <<mainloop:recordio,record-based I/O>> has been added.
68 * Added support for <<trans:,resource pools and transactions>>, which is a general
69 mechanism for tracking resources and reporting errors. It is still considered
70 experimental, so the API can change in future releases.
72 * Added a growing array module `gary.h`, similar to `gbuf.h`, but with
73 a much more convenient interface.
75 * The <<lists:,Circular linked lists>> can recognize unlinked nodes,
76 see <<lists:fun_clist_unlink,`clist_unlink()`>>.
78 * Added `strtonum.h` -- a module for precise parsing of numbers.
80 * When compiled by a recent enough GCC, `__thread` is used for thread-local variables,
81 which is more efficient than the POSIX per-thread storage.
82 ** *Incompatible:* `ucwlib_context->thread_id` is no longer available directly,
83 please use ucwlib_thread_id() instead.
85 * *Incompatible:* Several modules have been declared obsolete and removed:
86 ** `sighandler` -- generic signal handling (it still exists internally)
87 ** `qache` -- a mmap-based shared cache
88 ** `prefetch` -- an interface to memory prefetch instructions; superseded by GCC `__builtin_prefetch`
89 ** `randomkey` -- a generator of cryptographically strong pseudo-random tokens; will be replaced
90 by something more generic soon
91 ** `profile` -- a profiling hack
93 * *Incompatible:* Several modules now have their own header files:
94 ** `process.h` -- all functions related to processes, previously declared in `lib.h`
95 ** `io.h` -- functions related to files from `lib.h` and `lfs.h`
96 ** `time.h` -- timestamps and interval timers, previously in `lib.h`
98 * *Incompatible:* Several configuration options were renamed or removed:
99 ** `CONFIG_FAKE_ELTPOOL` → `CONFIG_UCW_FAKE_ELTPOOL`
100 ** `CONFIG_LARGE_FILES` → `CONFIG_UCW_LARGE_FILES`
101 ** `CONFIG_OWN_GETOPT` → `CONFIG_UCW_OWN_GETOPT`
102 ** `CONFIG_DIRECT_IO` → `CONFIG_UCW_DIRECT_IO`
103 ** `DEFAULT_CONFIG` → `CONFIG_UCW_DEFAULT_CONFIG`
104 ** `ENV_VAR_CONFIG` → `CONFIG_UCW_ENV_VAR_CONFIG`
105 ** `CONFIG_LFS` was removed
106 ** `CONFIG_URL_ESCAPE_COMPAT` was removed
108 * `UCW::Configure` supports running of test programs.
110 * `UCW::CGI` support multiple argument tables and UTF-8 mode. Also, it uses the
111 proper HTTP status codes when reporting errors.
113 * Implementation details of <<fastbuf:,fastbufs>> have changed. The new code checks
114 invariants more carefully, so it is possible that custom fastbuf back-ends which
115 are buggy now fail, although they previously seemed to work.
120 This was the first stand-alone release of LibUCW. Before that, LibUCW was developed
121 as a part of the http://www.ucw.cz/holmes/[Sherlock Holmes project].