应用程序/ MVC事件模型 [英] Application / MVC Event Model

问题描述

更新：这个问题的灵感来自于我的更大的追求，将本体论映射到整个软件系统架构enchilada。 我'我写了一篇关于它的博文，希望这将有助于澄清我以后的情况。

Update: This question was inspired by my larger quest for mapping ontologically the whole software systems architecture enchilada. I've written a blog post about it, and hopefully it will help clarify what I'm after.

事件驱动的许多，许多，许多框架和堆栈对我的小脑袋来说有太多的变化。有没有一些资源可以定义一个合理的应用程序事件模型的大纲，哪些事件有哪些是最常见的触发器？

Many, many, many frameworks and stacks that's event-driven have too much variation for my little head to get around. Is there somewhere some resources that defines the outline of a reasonable Application Event Model, what events there are, and what triggers are most common?

我有自己的框架使用插件和事件驱动的架构，但我想要开源，因此希望使其更接近一些共同点，不要疏远人们。

I've got my own framework with a plugin and event-driven architecture, but I want to open-source it, and as such would like to make it closer to some common ground as not to alienate people.

所以澄清一下这是一个应用程序，意味着设置环境，依赖关系，数据源（如数据库），以及作为MVC框架设置模型，视图，启动控制器/动作，以及GUI界面的各个阶段（标题，内容，列等）。

So to clarify; this is for an application, meaning setting up the environment, the dependencies, the data sources (like databases), and being a MVC framework setting up the model, the view, launching controllers / actions, and in the GUI various stages of the interface (header, content, columns, etc.).

想法？思考？指针？ （此时我已经把语言和平台中立了）

Ideas? Thoughts? Pointers? (And I've made it language and platform neutral at this point)

推荐答案

我读了你的博客条目，一个非常有趣的阅读，但...这个问题似乎没有反映出你在这里提出的问题的广泛性。

I read your blog entry, which btw I found an extremely interesting read, but... this question does not seem to reflect the broadness of the issue you are presenting there.

你以后是非常抽象和理论的。我想说的是，如果你把这些想法与实际的技术相结合，你就会发现自己被卡住了。这就是为什么我们中许多人不愿意使用任何框架。特别是重贴产品突然声称符合趋势。我们主要基于什么似乎需要达到预定的结果。

What you are after is very abstract and theoretical. What I mean to say is that if you tie any of those ideas to actual technology you will find yourself 'stuck' with it. This is why many of us are reluctant to use any framework. Especially the 'relabeled' products suddenly claiming to conform to the trend. We choose mainly on the basis of what appears to be needed to reach a predetermined result.

针对应用程序体系结构域的框架（或一般的工具）主要区别于他们设计承担的责任的数量。春天例如只涉及去耦的概念，因此很容易在许多情况下被采用和使用。任何框架的质量都表示为这些框架的设计者能够如何将其产品保持在该责任范围之内。一些前端产品将完全相反，代码生成器是最糟糕的之一。

Frameworks (or tools in general) that target the application architecture domain distinguish themselves primarily by the amount of responsibility they are designed to take on. Spring for example only deals with the concept of decoupling and is therefore easily adopted and useable in many situations. The quality of any framework is expressed in terms of how well the designers of such frameworks were able to keep their products within the boundaries of that responsibility. Some front-to-end products will do exactly the opposite, code generators being among the 'worst' of them.

要在此页面顶部回答您的问题，我不认为现在有一个框架可以做你想要的，我不认为应用程序（应该）如何工作的单一模型。请记住，应用程序体系结构域比概念处理技术更多。换句话说：如果它的工作和满足要求，那么你已经完成了。

To answer your question at the top of this page, I do not think there is a framework that does what you want at this time and I do not think there is a single model of how applications (should) work. Keep in mind though that the application architecture domain deals with technology more than it does with concepts. In other words: If it works and meets the requirements, then you're pretty much done.

那就是说，你可能会在基于代理的系统中找到一些有价值的东西。

That said, you might find something of value in agent-based systems.

这篇关于应用程序/ MVC事件模型的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！