Content deleted Content added
Removed a double space and fixed a run-on sentence. There was no other mistake, so until it has more citations added it won't need copyedited again. |
Removed Template:Multiple issues and General fixes |
||
Line 1:
In [[distributed computing]], '''code on demand''' is any technology that sends executable software code from a server computer to a client computer upon request from the client's software. Some well-known examples of the code on demand paradigm on the web are [[Java applet]]s, Adobe's [[ActionScript]] language for the [[Adobe Flash Player|Flash Player]], and [[JavaScript]].<ref name="Is Code Still Moving Around">{{cite book|last= Carzaniga|first=Antonio|author2=Gian Pietro Picco |author3=Giovanni Vigna |year=2007|title=Is Code Still Moving Around? Looking Back at a Decade of Code Mobility|journal=ICSE COMPANION '07 Companion to the Proceedings of the 29th International Conference on Software Engineering|publisher=IEEE Computer Society|___location=Washington, DC, USA|pages=9–20|url=http://dl.acm.org/citation.cfm?id=1248922|doi=10.1109/ICSECOMPANION.2007.44|isbn=978-0-7695-2892-2|citeseerx=10.1.1.119.5295}}</ref>
Line 5:
Code on demand is a specific use of [[mobile code]], within the field of [[code mobility]].<ref name="Understanding Code Mobility">{{cite journal|last=Fuggetta|first=Alfonso|author2=Gian Pietro Picco|author3=Giovanni Vigna|year=1998|title=Understanding Code Mobility|url=http://www2.computer.org/portal/web/csdl/abs/trans/ts/1998/05/e0342abs.htm|journal=IEEE Transactions on Software Engineering|volume=24|issue=5|pages=342–361|doi=10.1109/32.685258|issn=0098-5589|accessdate=29 July 2009|citeseerx=10.1.1.20.3442}}</ref>
== Constraints ==
=== Client-Server ===
Line 16 ⟶ 17:
To further simplify interactions between clients and servers, the second constraint is that the communication between them must be stateless.
This means that all information about the client’s session is kept on the client, and the server is completely unaware. The consequence is that each request must contain all information necessary to perform the request (i.e. it cannot rely on any context information).
=== Cache ===
| |||