[Epo-ec-advisors] Some thoughts on areas to address in the EC

[mike at altrion.org]

> 2009/7/17 Matt S Trout <m.trout at shadowcat.co.uk>:
>> And, of course, the difference here is we don't need consensus that a
>> particular way is -best-, only that it's -popular- and -good-. This has
>> to
>> be an exercise in shipping rather than one in perfectionism.
>
> Correct.
>
> However...
>
> I may be reading people wrong, but I do think I'm already seeing the
> emergence of similar tendencies.

I hope not.

> "On top of that, I'm working on MQI (Message Queue Interface),
> which is intended to be DBI for messaging with a standard API via a
> factory class and MQD (driver) layers on top of each protocol. Thoughts?
> Does that sound like a good way forward?"
>
> This line of thought can quickly become "And we should build it and
> bundle it into the core"

MQI's being written because there appears to be a hole where it needs to
fit, not because 'we need something new in the EC'. I'd still be writing
it if the EC didn't exist, I think.