Instead of syncing data between the client and server via HTTP, volt uses a persistent connection between the client and server. When data updated on one client, it is updated in the database and any other listening clients. (With almost no setup code needed)
---
In .NET land, I used SignalR when it first came out and it has since been baked into ASP.Net.
In Rails, I use Pusher, a paid for service because it's just easy to use and iterate.
If this works like it says on the tin I am excited! Beyond excited! My one question though is how many users can it support? How many people can be 'listening' for a broadcast.
Comments
This is the interesting bit for me personally:
Instead of syncing data between the client and server via HTTP, volt uses a persistent connection between the client and server. When data updated on one client, it is updated in the database and any other listening clients. (With almost no setup code needed)
---
In .NET land, I used SignalR when it first came out and it has since been baked into ASP.Net.
In Rails, I use Pusher, a paid for service because it's just easy to use and iterate.
If this works like it says on the tin I am excited! Beyond excited! My one question though is how many users can it support? How many people can be 'listening' for a broadcast.
SignalR is not really baked into Asp.Net, it's only a gem (=Nuget Package) away though.