Code mobility

In distributed computing, code mobility is the ability for running programs, code or objects to be migrated (or moved) from one machine or application to another.[1] This is the process of moving mobile code across the nodes of a network as opposed to distributed computation where the data is moved.

It is common practice in distributed systems to require the movement of code or processes between parts of the system, instead of data.[1]

Examples of code mobility include scripts downloaded over a network (for example JavaScript, VBScript), Java applets, ActiveX controls, Flash animations, Shockwave movies (and Xtras), and macros embedded within Microsoft Office documents.[2]

Overview

The purpose of code mobility is to support sophisticated operations. For example, an application can send an object to another machine, and the object can resume executing inside the application on the remote machine with the same state as it had in the originating application.

According to a classification proposed by Fuggetta, Picco and Vigna,[1] code mobility can be either strong or weak: strong code mobility involves moving both the code, data and the execution state from one host to another, notably via a process image (this is important in cases where the running application needs to maintain its state as it migrates from host to host), while weak code mobility involves moving the code and the data only. Therefore, it may be necessary to restart the execution of the program at the destination host.

Several paradigms, or architectural styles, exist within code mobility:[1]

Implementations

Within code mobility, the Mobile Agent paradigm has conventionally attracted the most interest and research,[3] however some recent work has produced general purpose implementations.[4]

Mobile agent frameworks
General purpose

Mobile code can also be encapsulated or embedded in other file formats not traditionally associated with executable code. An example of this form of encapsulation is the presence of JavaScript in a PDF.[6]

Viruses

Mobile code can also download and execute in the client workstation via email. Mobile code may download via an email attachment (e.g., macro in a Word file) or via an HTML email body (e.g., JavaScript). For example, the ILOVEYOU, TRUELOVE, and AnnaK email viruses/worms all were implemented as mobile code (VBScript in a .vbs email attachment that executed in Windows Scripting Host). In almost all situations, the user is not aware that mobile code is downloading and executing in their workstation.

Renting code

Mobile code also refers to code "used for rent", a way of making software packages more affordable. i.e. to use on demand. This is specially relevant to the mobile devices being developed which are cellular phones, PDAs, etc. all in one. Instead of installing software packages, they can be "leased" and paid for on a per-usage basis.

See also

References

  1. 1 2 3 4 Fuggetta, Alfonso; Gian Pietro Picco; Giovanni Vigna (1998). "Understanding Code Mobility". IEEE Transactions on Software Engineering. NJ, USA: IEEE Press Piscataway. 24 (5): 342–361. ISSN 0098-5589. doi:10.1109/32.685258. Retrieved 29 July 2009.
  2. ↑ Dr Lawrie Brown. "Mobile Code Security". Australian Defence Force Academy. Retrieved 23 April 2012.
  3. ↑ Carzaniga, Antonio; Gian Pietro Picco; Giovanni Vigna (2007). "Is Code Still Moving Around? Looking Back at a Decade of Code Mobility". ICSE COMPANION '07 Companion to the proceedings of the 29th International Conference on Software Engineering. Washington, DC, USA: IEEE Computer Society: 9–20. doi:10.1109/ICSECOMPANION.2007.44.
  4. 1 2 "Mobility-RPC - Seamless Code Mobility and RPC for the Java platform". Retrieved 15 June 2012.
  5. ↑ "Mobile-C: a Multi-Agent Platform for Mobile C/C++ Agents". Retrieved 15 June 2012.
  6. ↑ "Acrobat JavaScript Specification" (PDF). Retrieved 18 November 2009.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.