Framework separated migration for web applications

Kwon, Jin-woo; Oh, Jin-Seok; Jeong, InChang; Moon, Soo-Mook

doi:10.1109/estimedia.2015.7351767

Cited by 3 publications

(2 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We found that, once the objects are completely created, there is no way to distinguish between them. In our previous approach, we suggested a naïve solution that we listed the built‐in objects and framework objects manually. That is, we manually inspected browser states and frameworks and listed up the object paths to the built‐in objects and the framework objects ahead of execution.…”

Section: Design Of Fsmmentioning

confidence: 99%

“…This paper is a revised and expanded version of a paper published in the 13th IEEE Symposium on Embedded Systems for Real‐time Multimedia (ESTIMedia 2015), Amsterdam, Netherlands, October 2015, in which we have proposed a preliminary design of separating frameworks from app states during a web app migration. We extended the paper as follows: First, we employed a monitoring system to automatically detect the built‐in objects and framework objects (Section 3.4.1).…”

mentioning

confidence: 99%

See 1 more Smart Citation

Lightweight migration for web applications with framework separation

2017

Self Cite

View full text Add to dashboard Cite

Web applications (apps) are programs created by web technologies such as HTML, CSS, and JavaScript. Web apps can be executed on any platform that supports a web browser. Such portability allows an interesting user experience called app migration, which can save an app's execution state to a file called snapshot, transmit it to another device, and continue the execution using the snapshot. However, existing approaches save all the states of the current app, regardless of its relevance to an app's state, making the snapshot size and snapshot creation time infeasibly large. For example, web apps are often programmed using web frameworks such as jQuery, which are libraries written in JavaScript to support app developments. We found that most objects created by frameworks during their initialization are not relevant to an app's state. Hence, one idea to reduce the snapshot size is not saving those framework objects in the snapshot but creating them after migration via re-initialization. Unfortunately, this is not always straightforward since the framework objects are intermingled with the app objects in the heap, possibly pointing to each other. To resolve this, we separated app objects that are attached to framework objects by monitoring app's execution and saved them to the snapshot. This paper proposes such a framework separated migration technique, with optimization to reduce the overhead, especially related to monitoring app's execution. With our approach, we could reduce the snapshot size by 89.1% on average and shorten the migration time by 47.6%, increasing the feasibility of app migration.

show abstract

Section: Design Of Fsmmentioning

confidence: 99%

mentioning

confidence: 99%