Kannel development version 0.9.1 released
Richard Braakman <[email protected]> Wed, 7 Jun 2000 00:14:23 +0300
| Newsgroups | gmane.comp.mobile.kannel.announce |
|---|---|
| Message-ID | <[email protected]> |
This is another development version. It should be usable for experimentation and testing but is not intended for production use. Please do try it out and report problems to [email protected] (the development mailing list) or [email protected] (the bug tracking system). Change summary from version 0.9: * New HTTP implementation used everywhere, and the old one has been dropped. * New bearerbox is in use, and the old one has been dropped. * All boxes now share a single configuration file, with a new format. * Wapbox mostly rewritten. New version is closer to the standard, less buggy, and will be easier to improve further. * WML compiler now uses the string table to compress its output. * New test utility drive_wapbox, to test wapbox in isolation. * New test utility test_cimd2, which emulates a CIMD2 server. * New gwlib wrapper for sockets, to do high speed non-blocking I/O. Not in use yet. * New gwlib wrapper for threads, both to encapsulate them for portability and to provide a "wakeup" feature whereby threads that are blocked or sleeping can be woken by other threads. Will be used to improve the shutdown sequence in all boxes, and the suspend feature in the bearerbox. * New approach for packing and unpacking WTP and WSP PDUs. * Improved portability to Solaris and FreeBSD. * Thread-safe wrappers around system library functions known to be not thread-safe. * Bug fixes: + wsp_http.c no longer crashes wapbox after every request. + WTP layer correctly sets retransmission flag. + CIMD2: handle text messages longer than 140 characters correctly. + fakewap: fixed tid handling. + http: header names are compared case-insensitively. + wsp: corrected capability parsing for Motorola Timeport. * Known problems: + Still "cannot handle TR-Invoke.ind" in the logfiles. + drive_wapbox with more than 1 client crashes the wapbox for some people. + "checking" memory allocator is slow; configure --with-malloc=native if you want Kannel to handle more than three requests per second. + bearerbox/wapbox shutdown sometimes gets stuck and requires kill -9. See the ChangeLog for detailed information.