Remote scripting
technology
Remote scripting is a technology which allows scripts and programs that are running inside a browser to exchange information with a server. The local scripts can invoke scripts on the remote side and process the returned information.
The earliest form of asynchronous remote scripting was developed before XMLHttpRequest existed, and made use of very simple process: a static web page opens a dynamic web page (e.g. at other target frame) that is reloaded with new JavaScript content, generated remotely on the server side.
The XMLHttpRequest and similar "client-side script remote procedure call" functions, open the possibility of use and triggering web services from the web page interface.
The web development community subsequently developed a range of techniques for remote scripting in order to enable consistent results across different browsers. Early examples include JSRS library from 2000, the introduction of the Image/Cookie technique in 2000.
JavaScript Remote Scripting
JavaScript Remote Scripting (JSRS) is a web development technique for creating interactive web applications using a combination of:
HTML (or XHTML)
The Document Object Model manipulated through JavaScript to dynamically display and interact with the information presented
A transport layer. Different technologies may be used, though using a script tag or an iframe is used the most because it has better browser support than XMLHttpRequest
A data format. XML with WDDX can be used as well as JSON or any other text format.
Begin with the source’s own compact description: “Remote scripting” is technology. The dossier treats that line as a proposition to test through Remote, scripting and technology, not as a finished interpretation.
Why this record matters
The phrase “technology” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
The date and method of observation matter as much as the stated conclusion, especially where classification or consensus has changed. The source revision retrieved here is dated Apr 16, 2025. The linked authority identifier is Q5846483. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2000.
Scientific names, classifications and consensus can change while older terminology persists in catalogues and historical literature. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.
- Current terminology
- Classification context
- Finding cited technical literature
Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.
Three-step research path
- Establish the record: confirm the title “Remote scripting”, its source revision and the description used here.
- Expand the search: follow Remote scripting primary sources, Remote scripting archive and Remote research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Remote scripting”?
- Has classification or technical consensus changed since the cited source?
- Is the terminology current, historical or disputed?
Search terms from this dossier
This entry incorporates text from “Remote scripting” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.