this post was submitted on 25 Feb 2025
25 points (100.0% liked)

Web Development

3609 readers
38 users here now

Welcome to the web development community! This is a place to post, discuss, get help about, etc. anything related to web development

What is web development?

Web development is the process of creating websites or web applications

Rules/Guidelines

Related Communities

Wormhole

Some webdev blogsNot sure what to post in here? Want some web development related things to read?

Heres a couple blogs that have web development related content

CreditsIcon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 2 years ago
MODERATORS
snowe@programming.dev
erlingur@programming.dev
Ategon@programming.dev
25
EXTREME SERVER SIDE RENDERING (www.scd31.com)
submitted 2 days ago by Tablaste@linux.community to c/webdev@programming.dev
3 comments fedilink hide all child comments
 

Before we get into extreme server side rendering (XSSR), we have to talk about normal server side rendering (SSR). This comes in two flavours, which I'm calling old-school and new-school.

Old-school SSR involves having a server which uses some logic to create the HTML of the web page on-the-fly. For example, you might hit /users/39, and it might give you the details of user 39. These details might be from a database, or they might come from somewhere else. The important part is there's no corresponding 39.html on the disk. The HTML is created dynamically by the back-end server. On the front-end side, there's no JavaScript or other logic required to render the page. As a result, once the page is loaded, there's no ability for it to be dynamic.

New-school SSR is similar to old-school SSR, but it does involve a bit of front-end JavaScript logic.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] drjkl@programming.dev 2 points 2 days ago* (last edited 2 days ago)

This reminds me of something (far, far simpler) that I did long ago. I wrote a small webapp that continually queried various servers and would keep the connection open to push new blocks as the server-side async queries completed. I ran into output-buffering issues (probably from the reverse-proxy server, but I can't be certain at this point) and ended up appending a 1K block of commented-out non-printing unicode characters to ensure it would get flushed to the browser. I called it the plunger. Probably not the best solution ๐Ÿ˜