Network management application-oriented taxonomy of mobile code
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
We present an application-oriented taxonomy of mobile code. We use a novel approach to managing telecommunication networks as a vehicle for describing the concepts through demonstrating the use of several types of mobile code in innovative network and system management applications. To make a clear distinction between the types of mobile code, we use a terminology that follows the Java conventions originated with the term applet. Therefore, in our jargon, we have servlets, exflets, deglets and netlets. We point to a piglet as a type of mobile code that constitutes a security risk to the network. We deliberately avoided the term agent in our taxonomy. In this paper, this term is used to refer to a general concept of code autonomy. Our approach to managing networks addresses the issues in traditional client/server, or in this context manager/agent, network management systems like the amount of data that needs to be transmitted, problems inherent to heterogeneous environment, like interoperability issues, problems with maintainability of the software, etc. With the techniques based on mobile code, we can harness many interoperability issues and work toward plug-and-play networks (PnPnets) by applying mobile agents that can take care of many aspects of configuring and maintaining networks in an autonomous way.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it