Services
Technology Web App Development Mobile App Development Windows App Development Database Development UI/UX Development Cloud Development SEO Digital Marketing Guest Posting Content Writing Artificial Intelligence Data Science ERP Development CRM Development CMS Development LMS Development Business Listing Blockchain Technology Startup Promotion AI Tools Integration
Products
Data Converter Cleaner TUC - Unit Converter Import Export Survey Manager Tweet Controller
Developer
Article Blog Forum Interview Beginner News Startup Quiz
Users
Career
Apply Job Internship
Pricing
Login Sign Up Get a Quote

interview

Home Interviews Alternative approaches to "push" notifications without SignalR – MindStick
Ask Question

1 Answers

ICSM Computer
ICSM Computer 18 Jun 2025
Report Abuse

Here are alternative approaches to "push" notifications without SignalR:

1. Long Polling / AJAX Polling (Simplest)

  • The client periodically polls the server (e.g., every 10–30 seconds) asking, "Any new updates?"
  • If yes, the server returns data (e.g., "Article Approved", "Blog Deleted").

Pros:

  • Very easy to implement
  • Works on all browsers

Cons:

  • Not real-time
  • Wastes resources if nothing new most of the time

Use if:

  • You want simplicity and semi-live updates (e.g., every 30s)

2. Web Push Notifications

  • This is the browser-based push notification system via the Push API + Service Workers.
  • You need:
    • HTTPS
    • Service Worker registered in the browser
    • User permission to receive notifications
    • Backend to send a push payload (often using VAPID keys)

Pros:

  • Works even when the user is not on your site (if the browser is open)
  • Modern and reliable (used by Gmail, Facebook, etc.)

Cons:

  • Only supported in modern browsers
  • Requires client-side setup with service workers
  • ASP.NET 4.7 needs a custom library to send Web Push (e.g., using WebPush.Net)

Use if:

  • You want true push notifications like mobile apps

3. Mobile Push Notifications (FCM, APNs)

If you're building a mobile or hybrid app, you can use:

  • Firebase Cloud Messaging (FCM) – for Android/web
  • Apple Push Notification Service (APNs) – for iOS

You can send push messages from your ASP.NET 4.7 backend using HTTP API calls to FCM/APNs.

Use if:

  • Your users are on mobile or you have a mobile app

4. Email Notifications

Simple but asynchronous.

  • User gets an email for events like article approval, blog deletion, etc.

5. In-App Notification System (Database-Based)

This is not real push, but works well with polling:

  • Store notifications in a DB (Notifications table).
  • Use AJAX polling to fetch unread notifications.
  • Show them in a dropdown or toast.

You can even combine this with SignalR/Web Push later if needed.

Which Should You Use?

Goal Best Option
Live in-page updates SignalR (best), else polling
Push to desktop browser Web Push API (with service worker)
Push to mobile Firebase / APNs
Simpler fallback AJAX polling + DB notifications
Asynchronous update Email/SMS/etc.

Summary:

Yes, in ASP.NET Framework 4.7, you can notify users without SignalR using:

  • AJAX polling
  • Web Push API
  • Mobile push APIs (FCM/APNs)
  • Emails or SMS
  • Database-driven in-app alerts
advertising
Markdown for AI

A clean, structured version of this page for AI assistants and LLMs.

Open .md