Skip to content
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

Multiple roots #109

Open
kuraga opened this issue Aug 9, 2013 · 2 comments
Open

Multiple roots #109

kuraga opened this issue Aug 9, 2013 · 2 comments

Comments

@kuraga
Copy link
Contributor

kuraga commented Aug 9, 2013

Hello! Next issue I want to attent is multiple roots issue.

We have a 'widget's root' termin: root of widget is its (sub)parent with nil parent (see here). Apotomo uses widgets' roots: here and here.

And widget is a root for itself after removing.

By other side we have (one only) request_processor.root: see here.

So, there are multiple roots in some situations.

Consider one (bad) situation. Consider widget (with awesome_root root) is responding to an event. According to this results of triggers go to widget.root.page_updates (awesome_root.page_updates). Suppose widget has been removed during responding. Then (according to this) widget.root is widget; and widget.root.page_updates is widget.page_updates but not awesome_root.page_updates. So, the result (page_updates) of respond is wrong.

You thoughts?

@apotonick
Copy link
Owner

Can you further describe how such a situation can be created? There should be only one root instance during the entire controller run.

@kuraga
Copy link
Contributor Author

kuraga commented Aug 16, 2013

'Consider one (bad) situation' paragraph?..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants