Midgard2 - flexibility rocks

There's much work done ( and much to be done still! ) to get clean and clear Midgard2. However I am quite impressed when I think how things look like now.

Core is just yet "another" library and proved to be quite usefull for:
language bindings, GTK applications , Apache modules or command line applications.
It's just the way how library should be built. Ah! I am very glad I can use midgard-core with libgda ( website seems to be refactored now ). At last I can forget about MySQL dependencies and its API.
As an addition, I also added openssl support today.

Apache module is just yet "another" Apache module. Unlike Midgard1 module, this one is "environment and language unaware". And it means that this module can be used with any language like perl, java or python.

And...this module forced me to create that "trick" in core , so you can initialize midgard library in GType system unaware application and use its power with forked GType aware child.

Today, new refactored midgard-apache module finds midgard hosts ( those prefixed too ) very well. Correctly parses uri to get midgard pages and nicely serves images attached to pages. This is very nice to notice correct 200, 404 or 403 :)

PHP extension is just yet "another" PHP extension. You can use it with php-cli scripts or just build websites.
( with MidCOM you do it quickly :)

Repligard functionality ( known from Midgard1 ) is just "yet another feature" of midgard-core.

I must say. It looks good :)

And what happens with stable 1.8 branch? I fixed few important issues related to midgard_collector, so we should have new 1.8.2 released very soon.