1.7.1 release delayed

Yesterday I sent mail to dev@midgard-project.org list about delayed release. The main reasons why I did it:

We have not fully confirmed memory leaks in latest stable release, and we couldn't confirm attachments bug. Luckily the second one is fixed now and seems like the first one should be too.

Quoting myself:
"The problem with memory leaks in midgard-php4 may be casued by default_properties hash initialized per every class per request and not fully freed at request end. Currently we do not fully follow Zend API to add class members and such members are directly added to zend_class_entry' default_properties hash.

Good news is that I managed to write wrapper which creates zend_entry_functions structure on the fly. It means that we do not have to set class members , but instead we create real object constructor. All objects initialized have properties set and classes which extend base midgard classes have also default members ( properties ) without any need to write own constructor.

And it means that we can register *all* midgard types found in all schemas when module is initialized. Only once when module is loaded and save valuable time when request is initialized. The only one problem here is that all classes are available for every host. To make it "safe" we can use
objects methods only and only when class exists in request schema. In any other case every method should return at least "Access denied"."

Now , good news is : new classes registration procedures are finished , seems to be very stable and what is more important we have the same support for PHP5.

I didn't manage ( yet ) to write additional macros which should refuse any method call for objects not defined in schema. But now I think it is not mandatory for 1.7 branch as we do not support any high level applications with new Midgard technologies.

So, we just wait for developers who test latest branch and we can release quite new release :)