-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Flyweight pattern for blocks in layout updates #29
Comments
@stalniy
Although this comment provides our best view of the product direction, priorities can change and features may be adjusted. As a result, we do not recommend making firm business decisions solely based on the information above. |
magento-team
pushed a commit
that referenced
this issue
Jan 16, 2015
[MPI] Performance improvements and bug fixes
Closed
ghost
mentioned this issue
May 26, 2015
Closed
1 task
5 tasks
4 tasks
4 tasks
5 tasks
5 tasks
ghost
mentioned this issue
Aug 10, 2022
5 tasks
ghost
mentioned this issue
Aug 19, 2022
5 tasks
5 tasks
5 tasks
Closed
5 tasks
This was referenced Feb 17, 2023
5 tasks
5 tasks
5 tasks
5 tasks
5 tasks
5 tasks
5 tasks
5 tasks
5 tasks
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think it's necessary to use Flyweight pattern for blocks in layout updates that does not have their own state information. In more cases when developer need only to display some template he uses a Mage_Core_Block_Template without any parameters for example
For such situation you can create "Context" object that will observe all parameters for block by his name. It can decrease usage of memory during displaying View part of system.
The text was updated successfully, but these errors were encountered: