Best choice for Long-polling / Comet in Java or C#?

Question

Which native server is best, in your opinion, to implement long-polling / Comet? The first target application is chat, but there will be other implementations - we basically need push-to-client capabilities.

I'm limiting the answers to C# or Java because these two technologies are dominant at my workplace. The requirements are as usual: performance, ease of deployment/programming, customization, ...

Degree

Answer 1

I just saw this blogpost from Scott Hanselman yesterday. It looks very promising.

http://www.hanselman.com/blog/AsynchronousScalableWebApplicationsWithRealtimePersistentLongrunningConnectionsWithSignalR.aspx

It features an opensource product called SignalR which is available through nuget.

You can find an example chat application in the sources @ github

https://github.com/SignalR/SignalR

Transformer

SignalR would be the best choice if .NET. Also in the ASP.net webstack – Thierry

Answer 2

Both Java and .NET platforms have enough capabilities to handle your needs. If you choose Java : You may start with DWR otherwise, on the .net side PokeIn library should be the choice.

Relive

DWR with Apache for JAVA | PokeIn with IIS/Apache/Ngix for .NET would be best – Rayburn

Answer 3

IIS + WebSync is a very straight-forward, scalable and extensible solution for server push. There is a free Community edition I highly recommend checking out.

Revile

Answer 4

Try netty-socketio project. It's a Java framework with long-pooling and websocket support using famous Socket.IO protocol.

Wheresoever

Answer 5

I don't think there's a significant difference in this regard.

Patter

Answer 6

I know that special attention was paid to Comet support in the Grizzly engine used by Glassfish. It wasn't treated as an afterthought.

Spade

That's interesting. What sort of special support does it have? – Patter