Content deleted Content added

Inline

Revision as of 18:51, April 13, 2025

TIMELINE

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

The official logo of HCDL. Illustrated by daughter of Lead Q-Language logic programmer. (Created by User:Recap, Author of Scope:Outbound)
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-X, and Q-WebAssembly.

The origin of the Hypercontent Distribution Language (HCDL) traces back to the early stages of the Q-Language framework’s development. Prior to the existence of Hypercontent protocols and their associated distribution languages, quantum-transistor computers rendered what could only be described as "primitive" websites. These early systems relied entirely on low-level, machine-specific instructions written in Q-Assembly, explicitly telling the machine what to display, line by line.

The lineage of HCDL also reaches further back into the years of Old Earth when web development was split across multiple languages: Hypertext Markup Language (HTML), Cascading Style Sheets (CSS), and JavaScript. These languages, though powerful in their time, lacked cohesion. The advent of quantum computation, particularly in its hybridized form, opened new frontiers for front-end development. It became clear that a unified and purpose-built language was needed, one that could harness the true potential of quantum-transistor infrastructure.

Thus emerged HCDL, a modern evolution of its fragmented ancestors. Today, websites are no longer static documents but fully interactive programs, constructed using THCDL (Textual HCDL), CSS-X, and Q-WebAssembly. These programs are compiled server-side, and through the Hypercontent Distribution Protocol (HCDP/HCSDP), a snapshot of the compiled program is sent to the client in response to their request. The snapshot is then executed within a sandboxed, isolated environment inside the client’s web browser, also the THOR Browser.

However, the infancy of HCDL was not without turbulence. In its first months, the mechanism of local program execution introduced a new attack vector. Because client-side execution initially lacked strict isolation, malicious actors could potentially exploit these program snapshots to gain access to the host system. This security lapse was addressed. Patches were rolled out, virtual isolation was enforced, and restrictions were imposed.

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.

HyperContent Secure Distribution Protocol

@@ Line 11: / Line 11: @@
 Thus emerged HCDL, a modern evolution of its fragmented ancestors. Today, websites are no longer static documents but fully interactive programs, constructed using THCDL (Textual HCDL), CSS-X, and Q-WebAssembly. These programs are compiled server-side, and through the Hypercontent Distribution Protocol (HCDP/HCSDP), a snapshot of the compiled program is sent to the client in response to their request. The snapshot is then executed within a sandboxed, isolated environment inside the client’s web browser, also the THOR Browser.
-However, the infancy of HCDL was not without turbulence. In its first months, the mechanism of local program execution introduced a new attack vector. Because client-side execution initially lacked strict isolation, malicious actors could potentially exploit these program snapshots to gain access to the host system. This security lapse was addressed. Patches were rolled out, virtual isolation was enforced, and restrictions were imposed.
+However, the infancy of HCDL was not without turbulence. In its first months, the mechanism of local program execution introduced a new attack vector. Because client-side execution initially lacked strict isolation, malicious actors could potentially exploit these program snapshots to gain access to the host system. This security lapse was addressed. Patches were rolled out, virtual isolation was enforced, and restrictions were imposed.[[File:HCDL.png|thumb|211x211px|class=skin-invert-image|File icon]]Filename Extension: {{inline-code|.hcdl}}
-Filename Extension: {{inline-code|.hcdl}}
 MIME type: {{inline-code|text/hcdl}}
-Type code: {{inline-code|TEXT}}[[File:HCDL.png|thumb|117x117px|class=skin-invert-image|File icon]]Some advantages of HCDL include:
+Type code: {{inline-code|TEXT}}
+Some advantages of HCDL include:
 *Lightweight
 *Highly optimised