signalr - Websockets in .NET 4.5 -

i want develop web application in client calls service on server action involves processing. server necessary processing , when updated data ready push data client. considering 2 approaches: - 1. using asp.net web api signalr 2. using websockets wcf in .net 4.5.

my server on windows server 2012 majority of client ie 9 think not support websockets.

as written in signalr documentation automatically falls long polling if websockets support not present without changing application code. whether supported websockets in .net 4.5 or have manually. means whether have implement both pull method , push method on server.

please guide me, approach have follow.

in later use case want build web application using phonegap create mobile app ios, android & windows phone.

websockets not fall longpolling (that doesn't make sense). signalr higher level abstraction on http transports , that's why fallback , other things (like provide nice programming model on connection).

if choose use websockets on asp.net (not sure wcf) you'll programming against raw sockets (this means reading/writing array segments etc) , doing job @ hard. signalr , fallback several other transports (forever frame, server sent events, longpolling) if websockets isn't available on client or server.

regarding clients, if choose use signalr you'll need use signalr client. have support javascript , .net (silverlight, windows phone 8, winrt, .net 4 , .net 4.5). people have written clients other platforms including ios , android don't maintain them can't speak how date are.

i'd recommend use signalr can focus on application logic instead of messing low level programming model of websockets.