Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
You must create an account or log in to edit.

Hypercontent Distribution Language

Scope: Distant Worlds
From Amaranth Legacy, available at amaranth-legacy.community
Revision as of 18:14, April 13, 2025 by MMONTAGEe (talk | contribs) (tess' explanation)
"ACROSS SPACE & TIME TOWARDS DISTANT WORLDS"
TIMELINE

This article takes place in the 24 & 26 centuries of Distant Worlds.

Article contributors: tesinormed

HCDL also known as the Hypercontent Distribution Language, is the standard binary language used in Web communications to end users. It is normally assembled on the server side using THCDL (textual HCDL), CSS, and Q-WebAssembly.

Filename Extension: .hcdl

MIME type: text/hcdl

Type code: TEXT

Some advantages of HCDL include:

  • Lightweight
  • Highly optimised
  • Reduced request load and page loading time due to preprocessing on the server side
  • On-the-fly parsing
  • Extreme modularity with numerous libraries
  • Native support in Q-Language-written Web browsers

Language

Example

HCDL
meta>
    title>Example Title;
<
header>
    header-l1>Title;
<
content>
    parag>attr>.red:.extra-class;HLLO
EXTRA TEXT;
    list>attr>unordered:.red;
        list-entry>whatever bold>text;;
    <
<

> a < — behaves like a standard opening tag. It begins a block element.

For self-closing tags that contain only text, you can omit the <. This simplifies the syntax for simple text insertions.

The difference between >; and > <:

>; expects text content or additional inline HCDL.

> < expects only more nested HCDL elements, no plain text.

: is used to separate attributes within a tag.

.red {
    color: red;
}

.extra-class {
    text-align: center;
}
fun onLoad() {
     Hcdl.selectElement(".extra-class").outer = parag {
         +"hello"
     }
}

The previous section would compile to:

HCDL
[0x1 META]
[0x1 TITLE]Title[0x2 TITLE]
[0x1 SCRIPT](Q-WebAssembly)[0x2 SCRIPT]
[0x2 META]
[0x1 HEADER]
[0x1 HEADER-L1]Title[0x2 HEADER-L1]
[0x2 HEADER]
[0x1 CONTENT]
[0x1 PARAG][0x1 ATTR].red:.extra-class[0x2 ATTR][0x1 COMPCSS DEDUPID=2114012]color:red[0x2 COMPCSS][0x1 COMPCSS DEDUPID=2941024]text-align:center[0x2 COMPCSS]Hi[0x2 PARAG]
[0x1 LIST][0x1 ATTR]unordered:.red[0x2 ATTR][0x1 COMPCSS DEDUPID=2114012][0x2 COMPCSS]Hi[0x2 LIST]
[0x2 CONTENT]

Hypercontent Distribution Protocol

The Hypercontent Distribution Protocol (HCDP) is an application-layer protocol (Layer 7 in the Internet protocol suite model) designed for distributed, collaborative, hypermedia information systems. As the evolutionary successor to the classical Hypertext Transfer Protocol (HTTP), HCDP forms the backbone of modern data communication across the World Wide Web, with support for advanced hypercontent structures, documents embedded with dynamic hyperlinks, rich media, and interactive references easily accessible via clicks, taps, or neural input (in compatible environments).

HCDP introduces compatibility with the Hypercontent Distribution Language (HCDL), a next-generation front-end development language. It enables fluid integration of multimedia elements, AI-driven UI components, and cross-platform accessibility in a decentralized environment (THOR Browser).

HCDP operates as a request–response protocol under the client–server model:

  • A client, typically a web browser or HCDL-capable interface, initiates a connection and sends an HCDP request.
  • A server, running a daemon or process hosting one or more web applications, processes the request and returns an HCDP response.

This response contains:

  • Completion status codes (e.g., 200 OK, 404 Not Found, etc.)
  • Optional payloads such as HCDL files, media content, or server-generated data.
  • HCDP supports both static and dynamic content, allowing developers to deliver immersive, data-rich user experiences.
HCDP Port Number is: 88

HyperContent Secure Distribution Protocol

HCDP Port Number is: 448
Note: The data transmitted via HCDP is unencrypted by default. All content, including sensitive information such as login credentials or session tokens, can be intercepted by network packet analyzers and monitoring tools. Use of HCDP for transmitting personal or confidential information is strongly discouraged. For secure communication, it is recommended to use HCSDP (the secure, quantum-encrypted variant of HCDP) which ensures data integrity and confidentiality via cryptographic tunneling.
Contents