ASP.NET - Utilizing Comet to send server messages to multiple clients

Question

ASP.NET - Utilizing Comet to send server messages to multiple clients

I am developing an application that relies on server-side variables which update every second. It is crucial that all clients viewing the webpage are able to see these updates in real-time.

Many people have suggested using comet as it allows for pushing/pulling of data every second. However, I have a few questions regarding this:

In terms of efficiency and accuracy, would it be better to pull the new data from the client or push it from the server, considering the need for updates every second?
Additionally, the item IDs on the server side (along with their corresponding variables) can change. When a client refreshes the page, they should still receive the most up-to-date and relevant IDs. What is the best way to implement this using jQuery/JavaScript on the client side?
Lastly, I am having trouble finding a reliable (and affordable) comet library/api for ASP.NET (C#). Has anyone had success using a comet library with similar requirements? We anticipate having up to 2000 comet connections active at any given time.

c#javascript asp.net comet

Answer 1

Answer №1

One of the standout features of the PokeIn ASP.NET ajax library is its SendToAll function, which allows for easy communication with multiple clients.

Answer 2

One of the standout features of the PokeIn ASP.NET ajax library is its SendToAll function, which allows for easy communication with multiple clients.

Answer 3

Answer №2

WebSync from Frozen Mountain is a powerful comet server designed for IIS and ASP.NET, offering seamless integration into your application stack to enable real-time data communication with a large number of clients per server node.

Make sure to explore the Community edition which is available for free!

Answer 4

WebSync from Frozen Mountain is a powerful comet server designed for IIS and ASP.NET, offering seamless integration into your application stack to enable real-time data communication with a large number of clients per server node.

Make sure to explore the Community edition which is available for free!

Answer 5

Answer №3

What is the most efficient solution for constantly updating data every second: pulling from the client or pushing from the server?

In my opinion, it doesn't matter too much as the time intervals are short between data requests and updates. I would suggest initiating a new XMLHttpRequest on the client side after each successful request. You could also consider sending the server the latest received data so it can compare with the current one and only respond when there is new data available.

I am facing an issue where item IDs on the server can change, and upon page refresh, the client needs to retrieve the oldest and currently active IDs. How can I ensure that my jQuery/JavaScript on the client side keeps track of these changing IDs?

If I understand correctly, you could store all name/value pairs in an object on the client side. When new variables are received, they won't overwrite existing data but rather update it with the latest values. It could be structured like this:

{ first_variable: 345,
  second_one: "foo",
  and_the_third: ["I", "am", "an", "array,", "hooray!"]
}

When a new value for `second_one` arrives, such as `"bar"`, the object would update like so:

{ first_variable: 345,
  second_one: "bar",
  and_the_third: ["I", "am", "an", "array,", "hooray!"]
}

I am struggling to find a good, affordable comet library/API for ASP.NET (C#). Has anyone had success using a comet library with C#?

While I lack experience with ASP.NET, have you considered writing your own server-side code to maintain an open connection and periodically check for state changes? This approach might eliminate the need for a specific library.

UPDATE: To demonstrate how to maintain an open connection on the server side, here is a PHP long-polling simulation I created:

<?php
  sleep(5);
?>
<b>OK!</b>

Rather than having the process sleep, you can continuously monitor for state changes in a loop. Additionally, instead of returning HTML elements, you can send back data, potentially in JSON format. Adapting this concept to ASP.NET/C# should not be overly complex.

Answer 6

What is the most efficient solution for constantly updating data every second: pulling from the client or pushing from the server?

In my opinion, it doesn't matter too much as the time intervals are short between data requests and updates. I would suggest initiating a new XMLHttpRequest on the client side after each successful request. You could also consider sending the server the latest received data so it can compare with the current one and only respond when there is new data available.

I am facing an issue where item IDs on the server can change, and upon page refresh, the client needs to retrieve the oldest and currently active IDs. How can I ensure that my jQuery/JavaScript on the client side keeps track of these changing IDs?

If I understand correctly, you could store all name/value pairs in an object on the client side. When new variables are received, they won't overwrite existing data but rather update it with the latest values. It could be structured like this:

{ first_variable: 345,
  second_one: "foo",
  and_the_third: ["I", "am", "an", "array,", "hooray!"]
}

When a new value for `second_one` arrives, such as `"bar"`, the object would update like so:

{ first_variable: 345,
  second_one: "bar",
  and_the_third: ["I", "am", "an", "array,", "hooray!"]
}

I am struggling to find a good, affordable comet library/API for ASP.NET (C#). Has anyone had success using a comet library with C#?

While I lack experience with ASP.NET, have you considered writing your own server-side code to maintain an open connection and periodically check for state changes? This approach might eliminate the need for a specific library.

UPDATE: To demonstrate how to maintain an open connection on the server side, here is a PHP long-polling simulation I created:

<?php
  sleep(5);
?>
<b>OK!</b>

Rather than having the process sleep, you can continuously monitor for state changes in a loop. Additionally, instead of returning HTML elements, you can send back data, potentially in JSON format. Adapting this concept to ASP.NET/C# should not be overly complex.

ASP.NET - Utilizing Comet to send server messages to multiple clients

Answer №1

Answer №2

Answer №3

Similar questions

Number each element in sequence

What steps can be taken to ensure that a JavaScript webpack module created for the browser can be safely loaded in a node environment?

It appears that using JQuery's .when and .done functions may result in the code executing before the script has finished loading

CrossBrowser - Obtain CSS color information

How to Retrieve a Date using Month, Week, and Day Numbers in JavaScript

Using Axios to Send a JSON Object with Nested Properties

Encountered an issue while executing the next build process

Utilizing jQuery to access Flash functions

The server nodejs is unable to recognize the dotenv file

Identifying Equivalent Connections

Troubleshooting Problem with JQuery Paginate Plugin Alignment

Problems with radio button serialization in jQuery form plugin

The query string in web forms consistently returns a null value

Steps for deactivating a button until the form has been submitted

How come I am unable to access a local JSON file using AngularJS $http?

Is there a way to track the number of visits by a 'user' to a website?

Is it necessary for a writable stream in NodeJS to wait for the drain event before writing again automatically?

Managing authentication tokens in next.js

Prevent TypeScript from generalizing string literals as types

When I try to insert LD JSON data into the script tag inside the helmet on schema.org, the google validator at validator.schema.org displays an error