blocks|key|564722|text|我知道这听起来很老套但是..。您考虑过使用"ModelFacade“作为facade类的类名吗？我认为，在文档中，该接口已经命名为Model，这看起来相对简单，并且非常清楚您使用的是哪种设计模式。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|564723|entityMap^0|M|B|1T|5|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

I know this seems trite, but... have you considered using "<code>ModelFacade</code>" as the class name for the facade class? I think with documentation that indicates that the interface was already named <code>Model</code>, it seems relatively straightforward, and makes it very clear which design pattern you're using.

blocks|key|564749|text|供应商和消费者呢？我想你是在你的问题中自己说的。也许生产者和*消费者是一个更好的匹配？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|564750|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

How about *Provider and *Consumer? I think you said it yourself in your question. Perhaps *Producer and *Consumer is a better match?

blocks|key|2142033|text|在我们团队的讨论中，提出了另一个选项:我们可以将现有的Model接口重命名为其他东西，只需调用新的外观Model即可。事实上，它们现在都可以被称为Model，因为它们将生活在单独的包中。(虽然我不喜欢不同名称空间中的同名类。)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2142034|entityMap^0|R|5|1F|5|21|5|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

In discussions within our team, another option has been proposed: we can rename the existing <code>Model</code> interface to something else, and just call the new façade <code>Model</code>. In fact, they can both be called <code>Model</code> right now, because they will live in separate packages. (Although I'm not a fan of identically-named classes in different namespaces.)

blocks|key|2142061|text|听起来，ModelInfo、ModelHost和ModelInstance都应该是Model的成员。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2142062|请参阅https://softwareengineering.stackexchange.com/questions/316840/is-it-bad-practice-to-name-a-class-with-a-facade-suffix，以了解为什么通常不应该使用特定的实现来命名类。基本上，有一天，您可能希望使用不同的模型实现，这碰巧不是一个外观。|offset|length|2142063|entityMap|0|LINK|mutability|MUTABLE|url|https://softwareengineering.stackexchange.com/questions/316840/is-it-bad-practice-to-name-a-class-with-a-facade-suffix^0|0|3|3A|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Sounds like ModelInfo, ModelHost, and ModelInstance should all be members of Model.

See <a href="https://softwareengineering.stackexchange.com/questions/316840/is-it-bad-practice-to-name-a-class-with-a-facade-suffix">https://softwareengineering.stackexchange.com/questions/316840/is-it-bad-practice-to-name-a-class-with-a-facade-suffix</a> for why you generally shouldn't name classes with the specific implementation used. Basically, some day you may want to use a different implementation of Model, which happens to not be a facade.

blocks|key|564737|text|PureMVC使用名为ApplicationFacade的单例，并使用在IFacade中定义的方法(如registerProxy+)注册所有模型。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|564738|entityMap^0|B|H|10|7|1F|D|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

PureMVC uses a singleton named <code>ApplicationFacade</code> and registers all the models with methods like <code>registerProxy</code> which are defined in <code>IFacade</code>

A little background: We're building a library/framework for working with scientific models. We have an interface <code>Model</code> which defines the operations that a model must implement, which is pretty minimal. That is: the <code>Model</code> interface defines the contract of a model from the point of view of a model implementor.

The framework adds a bunch of other functionality around the model, but right now client code has to access that functionality by using a bunch of other classes, such as <code>ModelInfo</code>, <code>ModelHost</code>, <code>ModelInstance</code>, etc.

In our application that uses this framework, we don't want to actually have to deal with all this mechanism of running models, etc. So we've decided to use the <a href="http://en.wikipedia.org/wiki/Facade_pattern">façade pattern</a> to wrap up the framework functionality in an easy-to-use object. (We've already applied this pattern to other parts of the framework, with good success.)

Here is the question: given that we already have an interface <code>Model</code>, what would be a good name for the façade class? The <code>Model</code> interface is the contract between the framework and the model implementation, and the new class will define the contract between the framework and the client application.

Or, more generally: when we have an abstraction provided by a library or framework, how can we name the "two sides" of the abstraction so as to clearly identify the "provider" and "consumer" interfaces to the abstraction?

(If it matters, for this project we're using Java 6.)

What's a good name for a façade class?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

一个小小的背景:我们正在为使用科学模型建立一个库/框架。我们有一个接口Model，它定义了模型必须实现的操作，这是非常小的。也就是说：Model接口从模型实现者的角度定义模型的契约。该框架在模型周围添加了许多其他功能，但是现在客户端代码必须使用一些其他类来访问该功能，如ModelInfo、ModelHost、ModelInstance等。在我们使用该框架的应用程序中，我们不想实际处理所有这些运行模

问门面课的好名字是什么？
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问门面课的好名字是什么？EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问门面课的好名字是什么？
EN