Not sure about the server side 2012 requirements but signalr drops to
polling iframes etc if websockets are not available I think.
On Wednesday, 8 April 2015, Greg Keogh g...@mira.net wrote:
Folks, our ASP.NET app can submit a job to the server for processing
which can take up to a minute or
Folks, our ASP.NET app can submit a job to the server for processing which
can take up to a minute or so. We've been looking at ways the client can
see progress on the server-side: * AJAX script could poll at intervals by
calling a web service method * A kit like SignalR could push notifications
SignalR will still work without WebSockets, it will fall back to long
polling I believe.
I created the demo app that broadcasts a fake stock ticker. I ran it
locally on my Win7 dev machine, then I deployed it to Azure. Fiddler
traffic shows that messages are very similar for each scenario and
Don't even get me started on javascript. I feel just as dirty using
javascript as I did with silverlight version 1. God save us
On Wednesday, 8 April 2015, Greg Keogh g...@mira.net wrote:
SignalR will still work without WebSockets, it will fall back to long
polling I believe.
I created the
SignalR will still work without WebSockets, it will fall back to long
polling I believe.
Craig
On Wed, Apr 8, 2015 at 10:50 AM, Greg Keogh g...@mira.net wrote:
Folks, our ASP.NET app can submit a job to the server for processing
which can take up to a minute or so. We've been looking at ways
http://macleodsawyer.com/2015/03/06/nine-truths-computer-programmers-know-that-most-people-dont/
You've pretty much described Fact #1. Everything is hacked together with
duct tape and coat hangers. :)
That's the beauty of it all. The power of Javascript is that you *can* hack
it together. Does
