Re: MidCOM and its further adaption to new Midgard versions - AKA Midgard core quality

Jukka Zitting <[email protected]> wrote:

> > Plan for 1.8 is very simple.
> >         * improved, faster and partially refactored core with QB
> >         * metadata for any midgard type
> >                 Maybe I am the only one who heard that
> >                 midcom's metadata is its killer?
> >         * Midgard Reflection
> >         * New Quota
> >         * New datatypes like ISO datetimes
> 
> And things like a new configuration mechanism, etc.

Excuse me? I think I do not understand.

> > If I would like to make parser improvements right now , how should I do
> > it after style mRFC has been passed? How caching features similiar to
> > MMP should look like after this mRFC has been passed? Should I move it
> > to midgard-php or midgard-apache? How should looks like request
> > handling?
> >
> > I asked these questions because no one focused on such "details" while
> > we voted for full rewrite of code in three midgard modules.
> 
> I answered all these questions when mRFC 0022 was discussed. The fact
> that I need to repeat myself over and over again is one reasons I feel
> so frustrated about taking any sort of responsibility over the
> architectural design. This problem is not related to just this issue
> but was repeated many times during the discussions last year.

I think I do not understand one thing here. Do we talk about discussions @dev 
or on #midgard or we talk about missed specs? 

Piotras