End-to-end data
4 important questions on End-to-end data
What is the problem of this chapter?
- application programs have to agree on the presentation format of data
- encoding must be efficient: compression
Contents
1. Presentation formating
2. Data compression
What is presentation formatting?
- from internal representation used by application
- into message that can be transmitted (marshalling)
- and vice versa (unmarshalling)
What data types are supported
- base: integers, floating point, characters
- flat: structures, arrays (with padding between fields)
- complex: trees, structures using pointers
What is argument marshalling?
- conversting base types from one representation to another
- packing sturctures (without padding)
- flattening complex structures
Conversion strategies
- canonical intermediate form
- receiver makes right
Tags: help to decode the message
- type, length
Stub
- module to implement marshaling
- Higher grades + faster learning
- Never study anything twice
- 100% sure, 100% understanding
Explain Network Data Representation
- very little use of tags
- receiver already knows what to do: typical for procedure call
- compiled stubs
- XDR unit = 4 bytes
- integer: 32 bit, two complement notation, big endian, signed or unsigned
- array: number of elements
Abstract Syntax Notation (ASN.1)
- ISO standard
- Basic Encoding Rules (BER)
- defines canonical intermediate form
- type tags
- integer: 32 bit, two complement, big endian, signed or unsigned
Network Data Representation (NDR)
- DCE standard
- receiver makes right
- compiled stubs
- no tags
The question on the page originate from the summary of the following study material:
- A unique study and practice tool
- Never study anything twice again
- Get the grades you hope for
- 100% sure, 100% understanding