What are two consequences of using the Composite View pattern?

What are two consequences of using the Composite View pattern?

What are two consequences of using the Composite View pattern?

A.
Improves performance

B.
Avoids duplicate content

C.
Forces a whole-part dependency

D.
Allows tables to be reused in multiple locations

E.
Restricts all sub views to have a consistent view technology



Leave a Reply 7

Your email address will not be published. Required fields are marked *


GRod

GRod

Improves Modularity and Reuse
The pattern promotes modular design. It is possible to reuse atomic portions of a template, such as a table of stock quotes, in numerous views and to decorate these reused portions with different information. This pattern permits the table to be moved into its own module and simply included where necessary. This type of dynamic layout and composition reduces duplication, fosters reuse, and improves maintainability.

Maybe A) is correct:

Performance Impact
Generating a display that includes numerous subviews may slow performance. Runtime inclusion of subviews will result in a delay each time the page is served to the client. In an environment with strict Service Level Agreements that mandate specific response times, such performance slowdowns, though typically extremely minimal, may not be acceptable. An alternative is to move the subview inclusion to translation time, though this limits the subview to changing when the page is retranslated.

Pesho

Pesho

A is daintily not correct.

Pesho

Pesho

I wonder about E though

Muhammad Asif Iqbal

Muhammad Asif Iqbal

B. As with Composite View you would have small portions of page and you can reuse any portion, so it will avoid duplicate contents.
D. A portion of a page can be a table, so it can be used in multiple locations.

Ashishkumar

Ashishkumar

BD

Why not A ? – Generating a display that includes numerous subviews may slow performance. Runtime inclusion of subviews will result in a delay each time the page is served to the client. In an environment with strict Service Level Agreements that mandate specific response times, such performance slowdowns, though typically extremely minimal, may not be acceptable. An alternative is to move the subview inclusion to translation time, though this limits the subview to changing when the page is retranslated.

Why not C ? – It is related to composite design pattern , not composite view.