3

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, ...

ripper234
  • 222,824
  • 274
  • 634
  • 905

6 Answers6

2

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.

Anton
  • 4,554
  • 2
  • 37
  • 60
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.

Ozzz
  • 300
  • 1
  • 7
2

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

Rik
  • 483
  • 3
  • 12
1

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

Nikita Koksharov
  • 10,283
  • 1
  • 62
  • 71
1

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

Steven Sudit
  • 19,391
  • 1
  • 51
  • 53
0

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

erickson
  • 265,237
  • 58
  • 395
  • 493