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

Virtual DOM as alternate to sandboxing #9

Open
3rd-Eden opened this issue Jun 13, 2014 · 3 comments
Open

Virtual DOM as alternate to sandboxing #9

3rd-Eden opened this issue Jun 13, 2014 · 3 comments

Comments

@3rd-Eden
Copy link
Member

We're currently sandboxing the CSS by namespacing it with the name of the pagelet. The JavaScript sandboxing will be done a future release when we enable our fortress module. The only thing left to sandbox is the DOM. And DOM sandboxing is hard, but due to recent brainfarts I came up with the idea of re-using the virtual DOM idea of react and implement a similar process in bigpipe.

It would solve the sandboxing issues as you would not be modifying the actual dom but a virual dom. In addition to sandboxing it would also introduce high performance as only a diff of the DOM will be updated instead of a complete update of each pagelet.

@jcrugzz
Copy link
Member

jcrugzz commented Jan 19, 2015

@3rd-Eden we should think about how we can make it possible to interop with something like react or other modules that handle this type of role. A way to make these types of solutions plugin to bigpipe well could be quite powerful.

@3rd-Eden
Copy link
Member Author

@jcrugzz So ideally, it would be a plugin then. Than we can switch between react, virtualdom & others.

@jcrugzz
Copy link
Member

jcrugzz commented Jan 19, 2015

@3rd-Eden yea thats my thought

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