China
Africa
Explore chapters and articles related to this topic
Computer-Aided Control System Design: Techniques and Tools
Published in Naim A. Kheir, Systems Modeling and Computer Simulation, 2018
François E. Cellier, C. Magnus Rimvall
Another interface, which is rarely even noticed by the casual CACSD software user, is the interface to a database in which results of computations, as well as programming modules, notebook files, and so on, may be stored. To promote the state of the art of CACSD software further, it is imperative that a database interface standard be defined. Lacking such a standard, most current CACSD software developers do not even offer a database interface but rely fully on the file-handling mechanism (directory structure) of the embedding operating environment. This mechanism is computationally efficient (the record manager, on every computer, is strongly optimized to suit the underlying hardware), but the mechanism is entirely insufficient for our task. The immediate effect of the lack of an appropriate database concept is a jungle of small and smallest data and program files scattered over different subdirectories, which makes it hard to retrieve data and programs that were previously stored for later reuse. As an example, a particular A matrix of a linear system is probably not related to the problem under investigation at all but is stored as a nonmnemonic file A.DAT located somewhere in the directory structure of the underlying operating system. Little has been done to address this pertinent problem. Probably most advanced in this context is the work of Maciejowski (1984) and Maciejowski and Szymkat (1994).
Streaming Media and Metafiles
Published in Joe Follansbee, Hands-On Guide to Streaming Media, 2006
Here’s the URL taken apart, piece by piece. Protocol – This is the streaming protocol used by the server. In the example, it’s Microsoft Media Services protocol. Note the following colon and pair of forward slashes.Domain – This is the familiar string of characters ending in .com. Note the following optional colon.Port – The number in the example, 1755, identifies the requested service to the computer where the service lives, in this case Windows Media Services. The RTSP protocol uses port 554. Port numbers are usually optional.Mount point – The mount point is the beginning place in the streaming media server’s file system or directory structure where streaming files are located. The mount point is set in the server’s configuration files.Path – The directory or directories under the mount point where a specific file is located. A file could be located directly under the mount point.File name – The name of the file to stream. In the example, the .wmv extension signals it’s a Windows Media file.
Application-Specific Extensions in SDP
Published in Radhika Ranjan Roy, Handbook of SDP for Multimedia Session Negotiations, 2018
The “name” selector MUST NOT contain characters that can be interpreted as directory structure by the local operating system. If such characters are present in the file name, they MUST be percent encoded. Note that the “name” selector might still contain characters that, although not meaningful for the local operating system, might still be meaningful to the remote operating system (e.g., ‘\’, ‘/’, ‘:’). Therefore, implementations are responsible for sanitizing the input received from the remote endpoint before doing a local operation in the local file system, such as the creation of a local file. Among other things, implementations can percent-encode characters that are meaningful to the local operating system before doing file system local calls.
Usevalia: Managing Inspection-Based Usability Audits
Published in International Journal of Human–Computer Interaction, 2022
Raimel Sobrino-Duque, Juan Manuel Carrillo-de-Gea, Juan José López-Jiménez, Joaquín Nicolás Ros, José Luis Fernández-Alemán
Drupal provides functionality through the use of the so-called modules. A module in Drupal is a set of program files, images, data and style sheets organized into a directory structure that is stored in the server’s file system. Usevalia was developed as a custom module. Table 3 provides a brief description of the purpose of the files included in the directory structure depicted in Figure 10.