Re: midgard_guid_new and legacy objects

"Jukka Zitting" <[email protected]> wrote:

> Hi,

Hi,

> I have no clue on what you mean. :-)

Briefly:

I.
	1.7 - legacy and schema objects can be "transparently replaced"
	1.8 - we mark old API as obsolete
	1.9 - we implement Midgard Lite like old midgard-php API 
	For me there is some huge logicless step between 1.8 and 1.9.

II.
	Since 1.8 spider admin and Aegir's usage should be forbidden as those uis 
	creates objects without guids.

III. 
	Since 1.8 we do not use object's identifier as mgd structure's member but we use full object.
	So when you create person A with spider and you login in as person A, you use "guidless" person 
	object, and this is quite important for all metadata info.

To sum up:
Either we do mark old API as obsolete and we forget about Midgard Lite API 
or we do not mark old API as obsolete and we make legacy code ready for 1.9 now.

Piotras