10 May 10:37
CenterIcq: defects list.
Hello all, I have done some experiments with Centericq. Results are a bit frustrating. First of all, I discovered that Centericq uses its own, very heavily modified version of libicq2000. This means that you cannot update libicq2000 in your system to fix some errors in Centericq - you have to wait until Centericq guy(s) get the issue fixed. Ok, let's have a look at the modifications of libicq2000: 1. The library is compiled only as a static lib (funny, it has a double 'lib' prefix: liblibicq2000.a). Cool. We don't have to install a shared *.so anywhere - the code just links with the binary executable. This makes Centericq monolithic. I like the idea (no irony). 2. One small, but very useful modification: a transparent wrapper is added to a 'connect' call on the library sockets. This enables proxy support (great! Original libicq2000 cannot work through proxies). I LOVE this modification. But, of course, there is a price for it: we have to compile an additional library that contains the wrapper code (libconnwrap.a). It's tiny, so there is no problem with that. 3. Here we come to the most doubtful part: the removal of libsigc++. In essence, libsigc++ is a library that allows libicq2000 to work with callbacks. Yes, this library is huge. Yes, libicq2000 makes use only of a tiny part of libsigc++'s functionality. Yes, the latest version of libsigc++ is not compatible with libicq2000. But look what has been done: libsigc++ was replaced by some other implementation called sigslot(Continue reading)
RSS Feed