<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/from-page-refresh-to-fetch-the-pre-real-time-era-of-status-updates-in-asp-net-core-zvoga8qav" -->

---
title: From Page Refresh to fetch(): The Pre-Real-Time Era of...
description: An overview of client-driven techniques for checking on long-running server tasks in ASP.NET Core, tracing the evolution from full page refresh through...
canonical: https://daily.dev/posts/from-page-refresh-to-fetch-the-pre-real-time-era-of-status-updates-in-asp-net-core-zvoga8qav
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: From Page Refresh to fetch(): The Pre-Real-Time Era of Status Updates in ASP.NET Core | daily.dev
og:description: An overview of client-driven techniques for checking on long-running server tasks in ASP.NET Core, tracing the evolution from full page refresh through...
og:url: https://daily.dev/posts/from-page-refresh-to-fetch-the-pre-real-time-era-of-status-updates-in-asp-net-core-zvoga8qav
og:image: https://api.daily.dev/og/posts/ZVoga8qav.png
og:image:alt: From Page Refresh to fetch(): The Pre-Real-Time Era of Status Updates in ASP.NET Core
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# From Page Refresh to fetch(): The Pre-Real-Time Era of Status Updates in ASP.NET Core

**[We Are .NET](https://daily.dev/sources/wearedotnet)** · 8 min read · 2 upvotes · 0 comments

## Summary

An overview of client-driven techniques for checking on long-running server tasks in ASP.NET Core, tracing the evolution from full page refresh through XMLHttpRequest, jQuery's Ajax, native fetch() with short polling, and finally long polling. Each approach is illustrated with C# minimal API endpoints and JavaScript client code, along with trade-offs around latency, wasted requests, and server resource usage. This is framed as Part 1 of a two-part series, with Part 2 covering push-based Server-Sent Events and SignalR.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.binaryintellect.net/articles/9091cb0d-0da5-494a-a12c-0decb3bdb53b.aspx>

## Questions this post answers

### What is the difference between short polling and long polling for checking job status?

Short polling repeatedly asks the server at fixed intervals (e.g. every 3 seconds using setInterval and fetch), often getting a 'nothing new yet' answer, which wastes requests and adds latency up to one interval. Long polling instead holds the request open on the server until the status actually changes or a timeout occurs, cutting latency dramatically and reducing wasted round trips, at the cost of tying up a connection for longer.

_Comparing polling strategies before committing to one is easier with daily.dev surfacing real implementation trade-offs._

### How do you implement long polling in ASP.NET Core using a minimal API?

A minimal API endpoint accepts a CancellationToken and loops with a 25-second timeout, checking the status store every 500ms using Task.Delay so it doesn't block a thread; it returns immediately once the status changes, or returns the current state if the timeout is reached. This avoids blocking a thread while still holding the HTTP request open until new data arrives.

_Developers wiring up async status endpoints can find concrete ASP.NET Core patterns like this through daily.dev._

### What are the downsides of using full page refresh with a meta refresh tag to show status updates?

Full page refresh reloads the entire page and re-downloads all HTML, layout, stylesheets, and scripts just to reflect a small status change, causing jarring flicker, lost scroll position, and lost form state. It requires no JavaScript and works in any browser, but it cannot update just a progress bar or badge without redrawing everything, making it unsuitable beyond trivial status checks.

_Weighing simple versus modern update techniques gets easier when developers track these trade-offs on daily.dev._

## Similar posts on daily.dev

- [Real-Time at Last: SSE and SignalR in ASP.NET Core](https://daily.dev/posts/real-time-at-last-sse-and-signalr-in-asp-net-core-hfyl1qquh) · We Are .NET · 0 upvotes · 0 comments
- [Server-Sent Events in ASP.NET Core and .NET 10](https://daily.dev/posts/server-sent-events-in-asp-net-core-and-net-10-rqln4wisb) · Milan Jovanović · 25 upvotes · 0 comments
- [Why ASP.NET Core Feels Fast Locally but Slow in Production](https://daily.dev/posts/why-asp-net-core-feels-fast-locally-but-slow-in-production-mtgpu8lqk) · C\# Corner · 42 upvotes · 0 comments
- [Real-Time Systems for Web Developers: From Theory to a Live Go \+ React App](https://daily.dev/posts/real-time-systems-for-web-developers-from-theory-to-a-live-go-react-app-4z2t5olbb) · freeCodeCamp · 8 upvotes · 0 comments

---

Tags: [#webdev](https://daily.dev/tags/webdev), [#c#](https://daily.dev/tags/c#), [#aspnet](https://daily.dev/tags/aspnet)

[View this post on daily.dev](https://daily.dev/posts/from-page-refresh-to-fetch-the-pre-real-time-era-of-status-updates-in-asp-net-core-zvoga8qav)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"From Page Refresh to fetch(): The Pre-Real-Time Era of Status Updates in ASP.NET Core","url":"https://daily.dev/posts/from-page-refresh-to-fetch-the-pre-real-time-era-of-status-updates-in-asp-net-core-zvoga8qav","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/from-page-refresh-to-fetch-the-pre-real-time-era-of-status-updates-in-asp-net-core-zvoga8qav"},"datePublished":"2026-09-16T12:04:22.654Z","dateModified":"2026-09-16T12:04:47.739Z","description":"An overview of client-driven techniques for checking on long-running server tasks in ASP.NET Core, tracing the evolution from full page refresh through...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c8a79534e49ac840410a9d3b454135bf?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c8a79534e49ac840410a9d3b454135bf?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"We Are .NET","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"We Are .NET","logo":"https://media.daily.dev/image/upload/s--BsnVOa3i--/f_auto/v1718347410/logos/wearedotnet","url":"https://daily.dev/sources/wearedotnet"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/from-page-refresh-to-fetch-the-pre-real-time-era-of-status-updates-in-asp-net-core-zvoga8qav","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"webdev,c#,aspnet","timeRequired":"PT8M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"We Are .NET","item":"https://daily.dev/sources/wearedotnet"},{"@type":"ListItem","position":3,"name":"From Page Refresh to fetch(): The Pre-Real-Time Era of Status Updates in ASP.NET Core"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/from-page-refresh-to-fetch-the-pre-real-time-era-of-status-updates-in-asp-net-core-zvoga8qav#faq","mainEntity":[{"@type":"Question","name":"What is the difference between short polling and long polling for checking job status?","acceptedAnswer":{"@type":"Answer","text":"Short polling repeatedly asks the server at fixed intervals (e.g. every 3 seconds using setInterval and fetch), often getting a 'nothing new yet' answer, which wastes requests and adds latency up to one interval. Long polling instead holds the request open on the server until the status actually changes or a timeout occurs, cutting latency dramatically and reducing wasted round trips, at the cost of tying up a connection for longer. Comparing polling strategies before committing to one is easier with daily.dev surfacing real implementation trade-offs."}},{"@type":"Question","name":"How do you implement long polling in ASP.NET Core using a minimal API?","acceptedAnswer":{"@type":"Answer","text":"A minimal API endpoint accepts a CancellationToken and loops with a 25-second timeout, checking the status store every 500ms using Task.Delay so it doesn't block a thread; it returns immediately once the status changes, or returns the current state if the timeout is reached. This avoids blocking a thread while still holding the HTTP request open until new data arrives. Developers wiring up async status endpoints can find concrete ASP.NET Core patterns like this through daily.dev."}},{"@type":"Question","name":"What are the downsides of using full page refresh with a meta refresh tag to show status updates?","acceptedAnswer":{"@type":"Answer","text":"Full page refresh reloads the entire page and re-downloads all HTML, layout, stylesheets, and scripts just to reflect a small status change, causing jarring flicker, lost scroll position, and lost form state. It requires no JavaScript and works in any browser, but it cannot update just a progress bar or badge without redrawing everything, making it unsuitable beyond trivial status checks. Weighing simple versus modern update techniques gets easier when developers track these trade-offs on daily.dev."}}]}
```

