| 1 | <?xml version="1.0" encoding="UTF-8"?>
|
|---|
| 2 | <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
|
|---|
| 3 | "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
|
|---|
| 4 | <glossary id="Glossary">
|
|---|
| 5 | <glossdiv>
|
|---|
| 6 | <title>A</title>
|
|---|
| 7 |
|
|---|
| 8 | <glossentry>
|
|---|
| 9 | <glossterm>ACPI</glossterm>
|
|---|
| 10 |
|
|---|
| 11 | <glossdef>
|
|---|
| 12 | <para>Advanced Configuration and Power Interface, an industry
|
|---|
| 13 | specification for BIOS and hardware extensions to configure PC
|
|---|
| 14 | hardware and perform power management. Windows 2000 and higher as well
|
|---|
| 15 | as Linux 2.4 and higher support ACPI. Windows can only enable or
|
|---|
| 16 | disable ACPI support at installation time.</para>
|
|---|
| 17 | </glossdef>
|
|---|
| 18 | </glossentry>
|
|---|
| 19 |
|
|---|
| 20 | <glossentry>
|
|---|
| 21 | <glossterm>AHCI</glossterm>
|
|---|
| 22 |
|
|---|
| 23 | <glossdef>
|
|---|
| 24 | <para>Advanced Host Controller Interface, the interface that supports
|
|---|
| 25 | SATA devices such as hard disks. See <xref
|
|---|
| 26 | linkend="harddiskcontrollers" />.</para>
|
|---|
| 27 | </glossdef>
|
|---|
| 28 | </glossentry>
|
|---|
| 29 |
|
|---|
| 30 | <glossentry>
|
|---|
| 31 | <glossterm>AMD-V</glossterm>
|
|---|
| 32 |
|
|---|
| 33 | <glossdef>
|
|---|
| 34 | <para>The hardware virtualization features built into modern AMD
|
|---|
| 35 | processors. See <xref linkend="hwvirt" />.</para>
|
|---|
| 36 | </glossdef>
|
|---|
| 37 | </glossentry>
|
|---|
| 38 |
|
|---|
| 39 | <glossentry>
|
|---|
| 40 | <glossterm>API</glossterm>
|
|---|
| 41 |
|
|---|
| 42 | <glossdef>
|
|---|
| 43 | <para>Application Programming Interface.</para>
|
|---|
| 44 | </glossdef>
|
|---|
| 45 | </glossentry>
|
|---|
| 46 |
|
|---|
| 47 | <glossentry>
|
|---|
| 48 | <glossterm>APIC</glossterm>
|
|---|
| 49 |
|
|---|
| 50 | <glossdef>
|
|---|
| 51 | <para>Advanced Programmable Interrupt Controller, a newer version of
|
|---|
| 52 | the original PC PIC (programmable interrupt controller). Most modern
|
|---|
| 53 | CPUs contain an on-chip APIC ("local APIC"). Many systems also contain
|
|---|
| 54 | an I/O APIC (input output APIC) as a separate chip which provides more
|
|---|
| 55 | than 16 IRQs. Windows 2000 and higher use a different kernel if they
|
|---|
| 56 | detect an I/O APIC during installation. Therefore an I/O APIC must not
|
|---|
| 57 | be removed after installation.</para>
|
|---|
| 58 | </glossdef>
|
|---|
| 59 | </glossentry>
|
|---|
| 60 |
|
|---|
| 61 | <glossentry>
|
|---|
| 62 | <glossterm>ATA</glossterm>
|
|---|
| 63 |
|
|---|
| 64 | <glossdef>
|
|---|
| 65 | <para>Advanced Technology Attachment, an industry standard for hard
|
|---|
| 66 | disk interfaces (synonymous with IDE). See <xref
|
|---|
| 67 | linkend="harddiskcontrollers" />.</para>
|
|---|
| 68 | </glossdef>
|
|---|
| 69 | </glossentry>
|
|---|
| 70 | </glossdiv>
|
|---|
| 71 |
|
|---|
| 72 | <glossdiv>
|
|---|
| 73 | <title>B</title>
|
|---|
| 74 |
|
|---|
| 75 | <glossentry>
|
|---|
| 76 | <glossterm>BIOS</glossterm>
|
|---|
| 77 |
|
|---|
| 78 | <glossdef>
|
|---|
| 79 | <para>Basic Input/Output System, the firmware built into most personal
|
|---|
| 80 | computers which is responsible of initializing the hardware after the
|
|---|
| 81 | computer has been turned on and then booting an operating system.
|
|---|
| 82 | VirtualBox ships with its own virtual BIOS that runs when a virtual
|
|---|
| 83 | machine is started.</para>
|
|---|
| 84 | </glossdef>
|
|---|
| 85 | </glossentry>
|
|---|
| 86 | </glossdiv>
|
|---|
| 87 |
|
|---|
| 88 | <glossdiv>
|
|---|
| 89 | <title>C</title>
|
|---|
| 90 |
|
|---|
| 91 | <glossentry>
|
|---|
| 92 | <glossterm>COM</glossterm>
|
|---|
| 93 |
|
|---|
| 94 | <glossdef>
|
|---|
| 95 | <para>Microsoft Component Object Model, a programming infrastructure
|
|---|
| 96 | for modular software. COM allows applications to provide application
|
|---|
| 97 | programming interfaces which can be accessed from various other
|
|---|
| 98 | programming languages and applications. VirtualBox makes use of COM
|
|---|
| 99 | both internally and externally to provide a comprehensive API to 3rd
|
|---|
| 100 | party developers.</para>
|
|---|
| 101 | </glossdef>
|
|---|
| 102 | </glossentry>
|
|---|
| 103 | </glossdiv>
|
|---|
| 104 |
|
|---|
| 105 | <glossdiv>
|
|---|
| 106 | <title>D</title>
|
|---|
| 107 |
|
|---|
| 108 | <glossentry>
|
|---|
| 109 | <glossterm>DHCP</glossterm>
|
|---|
| 110 |
|
|---|
| 111 | <glossdef>
|
|---|
| 112 | <para>Dynamic Host Configuration Protocol. This allows a networking
|
|---|
| 113 | device in a network to acquire its IP address (and other networking
|
|---|
| 114 | details) automatically, in order to avoid having to configure all
|
|---|
| 115 | devices in a network with fixed IP addresses. VirtualBox has a
|
|---|
| 116 | built-in DHCP server that delivers an IP addresses to a virtual
|
|---|
| 117 | machine when networking is configured to NAT; see <xref
|
|---|
| 118 | linkend="networkingdetails" />.</para>
|
|---|
| 119 | </glossdef>
|
|---|
| 120 | </glossentry>
|
|---|
| 121 |
|
|---|
| 122 | <glossentry>
|
|---|
| 123 | <glossterm>DKMS</glossterm>
|
|---|
| 124 |
|
|---|
| 125 | <glossdef>
|
|---|
| 126 | <para>Dynamic Kernel Module Support. A framework that simplifies
|
|---|
| 127 | installing and updating external kernel modules on Linux machines; see
|
|---|
| 128 | <xref linkend="externalkernelmodules" />.</para>
|
|---|
| 129 | </glossdef>
|
|---|
| 130 | </glossentry>
|
|---|
| 131 | </glossdiv>
|
|---|
| 132 |
|
|---|
| 133 | <glossdiv>
|
|---|
| 134 | <title>E</title>
|
|---|
| 135 |
|
|---|
| 136 | <glossentry>
|
|---|
| 137 | <glossterm>EFI</glossterm>
|
|---|
| 138 |
|
|---|
| 139 | <glossdef>
|
|---|
| 140 | <para>Extensible Firmware Interface, a firmware built into computers
|
|---|
| 141 | which is designed to replace the aging BIOS. Originally designed by
|
|---|
| 142 | Intel, most modern operating systems can now boot on computers which
|
|---|
| 143 | have EFI instead of a BIOS built into them; see <xref
|
|---|
| 144 | linkend="efi" />.</para>
|
|---|
| 145 | </glossdef>
|
|---|
| 146 | </glossentry>
|
|---|
| 147 |
|
|---|
| 148 | <glossentry>
|
|---|
| 149 | <glossterm>EHCI</glossterm>
|
|---|
| 150 |
|
|---|
| 151 | <glossdef>
|
|---|
| 152 | <para>Enhanced Host Controller Interface, the interface that
|
|---|
| 153 | implements the USB 2.0 standard.</para>
|
|---|
| 154 | </glossdef>
|
|---|
| 155 | </glossentry>
|
|---|
| 156 | </glossdiv>
|
|---|
| 157 |
|
|---|
| 158 | <glossdiv>
|
|---|
| 159 | <title>G</title>
|
|---|
| 160 |
|
|---|
| 161 | <glossentry>
|
|---|
| 162 | <glossterm>GUI</glossterm>
|
|---|
| 163 |
|
|---|
| 164 | <glossdef>
|
|---|
| 165 | <para>Graphical User Interface. Commonly used as an antonym to a
|
|---|
| 166 | "command line interface", in the context of VirtualBox, we sometimes
|
|---|
| 167 | refer to the main graphical
|
|---|
| 168 | <computeroutput>VirtualBox</computeroutput> program as the "GUI", to
|
|---|
| 169 | differentiate it from the <computeroutput>VBoxManage</computeroutput>
|
|---|
| 170 | interface.</para>
|
|---|
| 171 | </glossdef>
|
|---|
| 172 | </glossentry>
|
|---|
| 173 |
|
|---|
| 174 | <glossentry>
|
|---|
| 175 | <glossterm>GUID</glossterm>
|
|---|
| 176 |
|
|---|
| 177 | <glossdef>
|
|---|
| 178 | <para>See UUID.</para>
|
|---|
| 179 | </glossdef>
|
|---|
| 180 | </glossentry>
|
|---|
| 181 | </glossdiv>
|
|---|
| 182 |
|
|---|
| 183 | <glossdiv>
|
|---|
| 184 | <title>I</title>
|
|---|
| 185 |
|
|---|
| 186 | <glossentry>
|
|---|
| 187 | <glossterm>IDE</glossterm>
|
|---|
| 188 |
|
|---|
| 189 | <glossdef>
|
|---|
| 190 | <para>Integrated Drive Electronics, an industry standard for hard disk
|
|---|
| 191 | interfaces. See <xref linkend="harddiskcontrollers" />.</para>
|
|---|
| 192 | </glossdef>
|
|---|
| 193 | </glossentry>
|
|---|
| 194 |
|
|---|
| 195 | <glossentry>
|
|---|
| 196 | <glossterm>I/O APIC</glossterm>
|
|---|
| 197 |
|
|---|
| 198 | <glossdef>
|
|---|
| 199 | <para>See APIC.</para>
|
|---|
| 200 | </glossdef>
|
|---|
| 201 | </glossentry>
|
|---|
| 202 |
|
|---|
| 203 | <glossentry>
|
|---|
| 204 | <glossterm>iSCSI</glossterm>
|
|---|
| 205 |
|
|---|
| 206 | <glossdef>
|
|---|
| 207 | <para>Internet SCSI; see <xref linkend="storage-iscsi" />.</para>
|
|---|
| 208 | </glossdef>
|
|---|
| 209 | </glossentry>
|
|---|
| 210 | </glossdiv>
|
|---|
| 211 |
|
|---|
| 212 | <glossdiv>
|
|---|
| 213 | <title>M</title>
|
|---|
| 214 |
|
|---|
| 215 | <glossentry>
|
|---|
| 216 | <glossterm>MAC</glossterm>
|
|---|
| 217 |
|
|---|
| 218 | <glossdef>
|
|---|
| 219 | <para>Media Access Control, a part of an Ethernet network card. A MAC
|
|---|
| 220 | address is a 6-byte number which identifies a network card. It is
|
|---|
| 221 | typically written in hexadecimal notation where the bytes are
|
|---|
| 222 | separated by colons, such as
|
|---|
| 223 | <computeroutput>00:17:3A:5E:CB:08</computeroutput>.</para>
|
|---|
| 224 | </glossdef>
|
|---|
| 225 | </glossentry>
|
|---|
| 226 |
|
|---|
| 227 | <glossentry>
|
|---|
| 228 | <glossterm>MSI</glossterm>
|
|---|
| 229 |
|
|---|
| 230 | <glossdef>
|
|---|
| 231 | <para>Message Signalled Interrupts, as supported by modern chipsets
|
|---|
| 232 | such as the ICH9; see <xref linkend="settings-motherboard" />. As
|
|---|
| 233 | opposed to traditional pin-based interrupts, with MSI, a small amount
|
|---|
| 234 | of data can accompany the actual interrupt message. This reduces the
|
|---|
| 235 | amount of hardware pins required, allows for more interrupts and
|
|---|
| 236 | better performance.</para>
|
|---|
| 237 | </glossdef>
|
|---|
| 238 | </glossentry>
|
|---|
| 239 | </glossdiv>
|
|---|
| 240 |
|
|---|
| 241 | <glossdiv>
|
|---|
| 242 | <title>N</title>
|
|---|
| 243 |
|
|---|
| 244 | <glossentry>
|
|---|
| 245 | <glossterm>NAT</glossterm>
|
|---|
| 246 |
|
|---|
| 247 | <glossdef>
|
|---|
| 248 | <para>Network Address Translation. A technique to share networking
|
|---|
| 249 | interfaces by which an interface modifies the source and/or target IP
|
|---|
| 250 | addresses of network packets according to specific rules. Commonly
|
|---|
| 251 | employed by routers and firewalls to shield an internal network from
|
|---|
| 252 | the Internet, VirtualBox can use NAT to easily share a host's physical
|
|---|
| 253 | networking hardware with its virtual machines. See <xref
|
|---|
| 254 | linkend="network_nat" />.</para>
|
|---|
| 255 | </glossdef>
|
|---|
| 256 | </glossentry>
|
|---|
| 257 | </glossdiv>
|
|---|
| 258 |
|
|---|
| 259 | <glossdiv>
|
|---|
| 260 | <title>O</title>
|
|---|
| 261 |
|
|---|
| 262 | <glossentry>
|
|---|
| 263 | <glossterm>OVF</glossterm>
|
|---|
| 264 |
|
|---|
| 265 | <glossdef>
|
|---|
| 266 | <para>Open Virtualization Format, a cross-platform industry standard
|
|---|
| 267 | to exchange virtual appliances between virtualization products; see
|
|---|
| 268 | <xref linkend="ovf" />.</para>
|
|---|
| 269 | </glossdef>
|
|---|
| 270 | </glossentry>
|
|---|
| 271 | </glossdiv>
|
|---|
| 272 |
|
|---|
| 273 | <glossdiv>
|
|---|
| 274 | <title>P</title>
|
|---|
| 275 |
|
|---|
| 276 | <glossentry>
|
|---|
| 277 | <glossterm>PAE</glossterm>
|
|---|
| 278 |
|
|---|
| 279 | <glossdef>
|
|---|
| 280 | <para>Physical Address Extension. This allows accessing more than 4 GB
|
|---|
| 281 | of RAM even in 32-bit environments; see <xref
|
|---|
| 282 | linkend="settings-general-advanced" />.</para>
|
|---|
| 283 | </glossdef>
|
|---|
| 284 | </glossentry>
|
|---|
| 285 |
|
|---|
| 286 | <glossentry>
|
|---|
| 287 | <glossterm>PIC</glossterm>
|
|---|
| 288 |
|
|---|
| 289 | <glossdef>
|
|---|
| 290 | <para>See APIC.</para>
|
|---|
| 291 | </glossdef>
|
|---|
| 292 | </glossentry>
|
|---|
| 293 |
|
|---|
| 294 | <glossentry>
|
|---|
| 295 | <glossterm>PXE</glossterm>
|
|---|
| 296 |
|
|---|
| 297 | <glossdef>
|
|---|
| 298 | <para>Preboot Execution Environment, an industry standard for booting
|
|---|
| 299 | PC systems from remote network locations. It includes DHCP for IP
|
|---|
| 300 | configuration and TFTP for file transfer. Using UNDI, a hardware
|
|---|
| 301 | independent driver stack for accessing the network card from bootstrap
|
|---|
| 302 | code is available.</para>
|
|---|
| 303 | </glossdef>
|
|---|
| 304 | </glossentry>
|
|---|
| 305 | </glossdiv>
|
|---|
| 306 |
|
|---|
| 307 | <glossdiv>
|
|---|
| 308 | <title>R</title>
|
|---|
| 309 |
|
|---|
| 310 | <glossentry>
|
|---|
| 311 | <glossterm>RDP</glossterm>
|
|---|
| 312 |
|
|---|
| 313 | <glossdef>
|
|---|
| 314 | <para>Remote Desktop Protocol, a protocol developed by Microsoft as an
|
|---|
| 315 | extension to the ITU T.128 and T.124 video conferencing protocol. With
|
|---|
| 316 | RDP, a PC system can be controlled from a remote location using a
|
|---|
| 317 | network connection over which data is transferred in both directions.
|
|---|
| 318 | Typically graphics updates and audio are sent from the remote machine
|
|---|
| 319 | and keyboard and mouse input events are sent from the client. A
|
|---|
| 320 | VirtualBox extension package by Oracle provides VRDP, an enhanced
|
|---|
| 321 | implementation of the relevant standards which is largely compatible
|
|---|
| 322 | with Microsoft's RDP implementation. See <xref linkend="vrde" /> for
|
|---|
| 323 | details.</para>
|
|---|
| 324 | </glossdef>
|
|---|
| 325 | </glossentry>
|
|---|
| 326 | </glossdiv>
|
|---|
| 327 |
|
|---|
| 328 | <glossdiv>
|
|---|
| 329 | <title>S</title>
|
|---|
| 330 |
|
|---|
| 331 | <glossentry>
|
|---|
| 332 | <glossterm>SAS</glossterm>
|
|---|
| 333 |
|
|---|
| 334 | <glossdef>
|
|---|
| 335 | <para>Serial Attached SCSI, an industry standard for hard disk
|
|---|
| 336 | interfaces. See <xref linkend="harddiskcontrollers" />.</para>
|
|---|
| 337 | </glossdef>
|
|---|
| 338 | </glossentry>
|
|---|
| 339 |
|
|---|
| 340 | <glossentry>
|
|---|
| 341 | <glossterm>SATA</glossterm>
|
|---|
| 342 |
|
|---|
| 343 | <glossdef>
|
|---|
| 344 | <para>Serial ATA, an industry standard for hard disk interfaces. See
|
|---|
| 345 | <xref linkend="harddiskcontrollers" />.</para>
|
|---|
| 346 | </glossdef>
|
|---|
| 347 | </glossentry>
|
|---|
| 348 |
|
|---|
| 349 | <glossentry>
|
|---|
| 350 | <glossterm>SCSI</glossterm>
|
|---|
| 351 |
|
|---|
| 352 | <glossdef>
|
|---|
| 353 | <para>Small Computer System Interface. An industry standard for data
|
|---|
| 354 | transfer between devices, especially for storage. See <xref
|
|---|
| 355 | linkend="harddiskcontrollers" />.</para>
|
|---|
| 356 | </glossdef>
|
|---|
| 357 | </glossentry>
|
|---|
| 358 |
|
|---|
| 359 | <glossentry>
|
|---|
| 360 | <glossterm>SMP</glossterm>
|
|---|
| 361 |
|
|---|
| 362 | <glossdef>
|
|---|
| 363 | <para>Symmetrical Multiprocessing, meaning that the resources of a
|
|---|
| 364 | computer are shared between several processors. These can either be
|
|---|
| 365 | several processor chips or, as is more common with modern hardware,
|
|---|
| 366 | multiple CPU cores in one processor.</para>
|
|---|
| 367 | </glossdef>
|
|---|
| 368 | </glossentry>
|
|---|
| 369 | </glossdiv>
|
|---|
| 370 |
|
|---|
| 371 | <glossdiv>
|
|---|
| 372 | <title>T</title>
|
|---|
| 373 |
|
|---|
| 374 | <glossentry>
|
|---|
| 375 | <glossterm>TAR</glossterm>
|
|---|
| 376 |
|
|---|
| 377 | <glossdef>
|
|---|
| 378 | <para>A widely used file format for archiving. Originally, this stood
|
|---|
| 379 | for "Tape ARchive" and was already supported by very early Unix
|
|---|
| 380 | versions for backing up data on tape. The file format is still widely
|
|---|
| 381 | used today, for example, with OVF archives (with an
|
|---|
| 382 | <computeroutput>.ova</computeroutput> file extension); see <xref
|
|---|
| 383 | linkend="ovf" />.</para>
|
|---|
| 384 | </glossdef>
|
|---|
| 385 | </glossentry>
|
|---|
| 386 | </glossdiv>
|
|---|
| 387 |
|
|---|
| 388 | <glossdiv>
|
|---|
| 389 | <title>U</title>
|
|---|
| 390 |
|
|---|
| 391 | <glossentry>
|
|---|
| 392 | <glossterm>UUID</glossterm>
|
|---|
| 393 |
|
|---|
| 394 | <glossdef>
|
|---|
| 395 | <para>A Universally Unique Identifier -- often also called GUID
|
|---|
| 396 | (Globally Unique Identifier) -- is a string of numbers and letters
|
|---|
| 397 | which can be computed dynamically and is guaranteed to be unique.
|
|---|
| 398 | Generally, it is used as a global handle to identify entities.
|
|---|
| 399 | VirtualBox makes use of UUIDs to identify VMs, Virtual Disk Images
|
|---|
| 400 | (VDI files) and other entities.</para>
|
|---|
| 401 | </glossdef>
|
|---|
| 402 | </glossentry>
|
|---|
| 403 | </glossdiv>
|
|---|
| 404 |
|
|---|
| 405 | <glossdiv>
|
|---|
| 406 | <title>V</title>
|
|---|
| 407 |
|
|---|
| 408 | <glossentry>
|
|---|
| 409 | <glossterm>VM</glossterm>
|
|---|
| 410 |
|
|---|
| 411 | <glossdef>
|
|---|
| 412 | <para>Virtual Machine -- a virtual computer that VirtualBox allows you
|
|---|
| 413 | to run on top of your actual hardware. See <xref
|
|---|
| 414 | linkend="virtintro" /> for details.</para>
|
|---|
| 415 | </glossdef>
|
|---|
| 416 | </glossentry>
|
|---|
| 417 |
|
|---|
| 418 | <glossentry>
|
|---|
| 419 | <glossterm>VMM</glossterm>
|
|---|
| 420 |
|
|---|
| 421 | <glossdef>
|
|---|
| 422 | <para>Virtual Machine Manager -- the component of VirtualBox that
|
|---|
| 423 | controls VM execution. See <xref linkend="technical-components" /> for
|
|---|
| 424 | a list of VirtualBox components.</para>
|
|---|
| 425 | </glossdef>
|
|---|
| 426 | </glossentry>
|
|---|
| 427 |
|
|---|
| 428 | <glossentry>
|
|---|
| 429 | <glossterm>VRDE</glossterm>
|
|---|
| 430 |
|
|---|
| 431 | <glossdef>
|
|---|
| 432 | <para>VirtualBox Remote Desktop Extension. This interface is built
|
|---|
| 433 | into VirtualBox to allow VirtualBox extension packages to supply
|
|---|
| 434 | remote access to virtual machines. A VirtualBox extension package by
|
|---|
| 435 | Oracle provides VRDP support; see <xref linkend="vrde" /> for
|
|---|
| 436 | details.</para>
|
|---|
| 437 | </glossdef>
|
|---|
| 438 | </glossentry>
|
|---|
| 439 |
|
|---|
| 440 | <glossentry>
|
|---|
| 441 | <glossterm>VRDP</glossterm>
|
|---|
| 442 |
|
|---|
| 443 | <glossdef>
|
|---|
| 444 | <para>See RDP.</para>
|
|---|
| 445 | </glossdef>
|
|---|
| 446 | </glossentry>
|
|---|
| 447 |
|
|---|
| 448 | <glossentry>
|
|---|
| 449 | <glossterm>VT-x</glossterm>
|
|---|
| 450 |
|
|---|
| 451 | <glossdef>
|
|---|
| 452 | <para>The hardware virtualization features built into modern Intel
|
|---|
| 453 | processors. See <xref linkend="hwvirt" />.</para>
|
|---|
| 454 | </glossdef>
|
|---|
| 455 | </glossentry>
|
|---|
| 456 | </glossdiv>
|
|---|
| 457 |
|
|---|
| 458 | <glossdiv>
|
|---|
| 459 | <title>X</title>
|
|---|
| 460 |
|
|---|
| 461 | <glossentry>
|
|---|
| 462 | <glossterm>XML</glossterm>
|
|---|
| 463 |
|
|---|
| 464 | <glossdef>
|
|---|
| 465 | <para>The eXtensible Markup Language, a metastandard for all kinds of
|
|---|
| 466 | textual information. XML only specifies how data in the document is
|
|---|
| 467 | organized generally and does not prescribe how to semantically
|
|---|
| 468 | organize content.</para>
|
|---|
| 469 | </glossdef>
|
|---|
| 470 | </glossentry>
|
|---|
| 471 |
|
|---|
| 472 | <glossentry>
|
|---|
| 473 | <glossterm>XPCOM</glossterm>
|
|---|
| 474 |
|
|---|
| 475 | <glossdef>
|
|---|
| 476 | <para>Mozilla Cross Platform Component Object Model, a programming
|
|---|
| 477 | infrastructure developed by the Mozilla browser project which is
|
|---|
| 478 | similar to Microsoft COM and allows applications to provide a modular
|
|---|
| 479 | programming interface. VirtualBox makes use of XPCOM on Linux both
|
|---|
| 480 | internally and externally to provide a comprehensive API to
|
|---|
| 481 | third-party developers.</para>
|
|---|
| 482 | </glossdef>
|
|---|
| 483 | </glossentry>
|
|---|
| 484 | </glossdiv>
|
|---|
| 485 | </glossary>
|
|---|
