2016
DOI: 10.1007/978-3-319-46963-8_12
|View full text |Cite
|
Sign up to set email alerts
|

Synchronizing Application State Using Virtual DOM Trees

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2017
2017
2021
2021

Publication Types

Select...
4
1

Relationship

2
3

Authors

Journals

citations
Cited by 13 publications
(3 citation statements)
references
References 14 publications
0
3
0
Order By: Relevance
“…Liquid software [22], also known as cross-device experience roaming [23], is a concept where software can dynamically flow between different computers, basically allowing execution of code and associated user experiences to be transferred dynamically and seamlessly from one computational element to another. While the majority of the work associated with liquid software has focused on the UI layer (e.g., [24][25][26]), the concept is applicable to any situation in which software can be dynamically redeployed and adapted to take full advantage of the storage and computational resources provided by different devices that are shared by one or multiple collaborating users.…”
Section: Towards Seamless Device-edge-cloud Continuummentioning
confidence: 99%
“…Liquid software [22], also known as cross-device experience roaming [23], is a concept where software can dynamically flow between different computers, basically allowing execution of code and associated user experiences to be transferred dynamically and seamlessly from one computational element to another. While the majority of the work associated with liquid software has focused on the UI layer (e.g., [24][25][26]), the concept is applicable to any situation in which software can be dynamically redeployed and adapted to take full advantage of the storage and computational resources provided by different devices that are shared by one or multiple collaborating users.…”
Section: Towards Seamless Device-edge-cloud Continuummentioning
confidence: 99%
“…In addition, their approach to expose closure variable lets any code to reach the closure variables, which is not desirable since the variables are secured on purpose. Voutilainen et al suggested Liquid Application Framework , which analyzes the state changes on the DOM during the runtime and saves the difference between the initial state and the current state using a technique named Virtual DOM . Their work can efficiently serialize a web app's state, but their work is mostly focused on the DOM tree.…”
Section: Related Workmentioning
confidence: 99%
“…In essence, building liquid web applications needs two facilities, (i) ability to relocate code freely across different computing environments; and (ii) ability to synchronize the state of the application across all devices running the code. In our previous work, we have used the DOM [26] and Web Components with Polymer [7] as the underlying technology. However, both technologies are closely tied to the browser, and target at the UI layer of web applications.…”
Section: Introductionmentioning
confidence: 99%