Topic: 下面情况用mediator恰当吗? |
Print this page |
1.下面情况用mediator恰当吗? | Copy to clipboard |
Posted by: bbskill Posted on: 2005-01-17 18:32 A把事件传给B,B处理后返回结果, A再依据结果改变自身。 在A和B之间弄一个mediator处理之间的通讯恰当吗? 还有B处理后返回的结果,A依据结果改变自身,应不应该 用observer模式来表示。还是只是把结果传给mediator,由 它来对A进行改变? 谢谢! |
2.Re:下面情况用mediator恰当吗? [Re: bbskill] | Copy to clipboard |
Posted by: emarket Posted on: 2005-01-17 23:33 这种情况用mediator 没有凸现 mediator的好处 : N*N--->N 如果参与放比较多,可以用mediator来减少component之间的耦合。 这里用observer比较合适, 我想你应该有一个state object, A 注册自己作为state object得listener, B可以改state object 这样用 observer比较合适。 另外完全什么模式都不用 也可以! |
3.Re:下面情况用mediator恰当吗? [Re: bbskill] | Copy to clipboard |
Posted by: bbskill Posted on: 2005-01-18 09:54 问题是A是view,B是model,我想让view和model减少耦合。 另外A和B可能也会影响到另一个view。 如果用observer模式,传送的结果数据比较多和频繁的时候,那效率会不会太低了。 A要改变的是它本身,如果加入state object,会不会使A的完整性减低, 还有使A和B之间的关系混乱? 万分谢谢。 |
4.Re:下面情况用mediator恰当吗? [Re: bbskill] | Copy to clipboard |
Posted by: floater Posted on: 2005-01-18 13:03 well, in your case, the model B *is* the state object. You may start with the simple approach - writing everything together, then try to refactor the code. Swing table view/model can easily handle thousands of rows. I am not sure how much data you have in your case. Try to be specific, don't try to generalize it, otherwise it's hard to see the benefit of good rules. Your first question is a generalized one. |
Powered by Jute Powerful Forum® Version Jute 1.5.6 Ent Copyright © 2002-2021 Cjsdn Team. All Righits Reserved. 闽ICP备05005120号-1 客服电话 18559299278 客服信箱 714923@qq.com 客服QQ 714923 |