Inside our MailerQ C++ application we've frequently used calls to 'dlopen()' - instead of using shared of static linking. There are a couple of good reasons why we've done this, which I'll explain in this article.

A couple of years ago I encountered a PHP framework that claimed to be based on the “Model View Controller” (MVC) pattern for the first time. When I heard about this, I was seriously surprised because PHP is not at all an appropriate programming language for making MVC applications. But nowadays there are many different PHP frameworks that also claim to be MVC – but as far as I have seen, this claim is still as ridiculous as it was for the first would-be MVC framework that I saw. PHP and MVC are not compatible with each other, and it is about time that we stop calling each PHP framework MVC.

Logging on and managing users, accounts and company information in Copernica can sometimes be confusing. Copernica is not a simple single-user system, but a multi-user, multi-account and multi-company environment. In this blog I will explain how these concepts relate to each other, and what consequences this has for licensing and invoicing.

MailerQ version 0.6 brings a number of new features. It has been six weeks since version 0.5 and the development team has managed to use this time to fix some bugs and add new features. Let's talk about the highlights.

We recently introduced a number of changes to our incident system. We have almost completely rewritten the system "under the hood" so that it is now fully integrated in the Copernica architecture. As a result of the changes, end users can now use their Copernica user name to access the full support history. We also changed the notification mails that are sent when the status of an incident changes, and made changes to the Copernica.com pages on which you can review our answer.