Skip to content

Commit aa9d276

Browse files
authored
Update over_the_wire.md
1 parent b3a2032 commit aa9d276

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

docs/advanced/technical/over_the_wire.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,19 @@
1-
# Key Idea: Over-the-Wire in abap2UI5
1+
# Over-the-Wire in SAP: The Key Idea of abap2UI5
22

33
The key idea of **abap2UI5** is to apply the principles of **Over-the-Wire** web development to the SAP ecosystem.
44

55
Over-the-Wire refers to a pattern where the server is responsible for rendering the user interface and sends ready-to-render HTML fragments to the browser. This avoids complex client-side frameworks and keeps the frontend lean and maintainable.
66

77
While this approach is widely used in frameworks like Hotwire, Livewire, or Phoenix LiveView, **abap2UI5 adapts this idea for the SAP technoligal environment**, using the SAP UI5 framework to render the UI based on server-provided definitions created in ABAP.
88

9+
+------------------------+ +-----------------------+ +--------------------+
10+
| ABAP Backend | | Browser | | User |
11+
|------------------------| |-----------------------| |--------------------|
12+
| - XML View Definition | --> | Receives JSON View | --> | Interacts with UI |
13+
| - JSON View-Model | | Renders with UI5 | | (clicks, inputs) |
14+
+------------------------+ +-----------------------+ +--------------------+
15+
16+
917
### History: From SSR to Over-the-Wire
1018

1119
In the early days of web development, Server-Side Rendering (SSR) was the standard approach. Every user interaction triggered a request to the server, which returned a fully rendered HTML page.

0 commit comments

Comments
 (0)