0

I want / have to implement a chat (like facebooks) in my web app. Through my research I've found two different approaches and I don't know which want I should take (to be honest I tried one but it has a strange behavior, but let me come to this later).

Some facts about my application. It has two different clients. One is a web-application, the other one is a wpf client. Both of these two clients should have implemented a chat. They communicate over a server via WCF-Services.

So, as I found out there is the comet approach which means AJAX Long Polling. On the other hand I can use WCF Callback Services.

Are there any dis/advantages of the WCF callback / Comet approach?

For me the callback approach is pretty straight forward, ajax long pooling sound much more complicated.

Thx's in advance

user1357096
  • 1

3 Answers3

1

I would offer you to try Reverse Ajax over PokeIn and benefit from the built-in WebSocket feature. You don't need anything else.

Nuray Altin
  • 1,294
  • 12
  • 19
0

Since you are looking at MS technology you'll probably be interested in reading this post by Brian Raymor who is a Senior Program Manager in the Windows Networking group at Microsoft.

SignalR is a good solution since it will choose a transport type suitable for the web browser that is making a connection. It won't work with IIS until Windows Server 8.

Your other options are XSockets, SuperWebSocket and more. See this realtime web tech guide (disclaimer: which I maintain)

You could also look at a hosted service. Again, there are options available in the guide I've provided a link to above.

leggetter
  • 15,248
  • 1
  • 55
  • 61
-1

I would check out SignalR for the Web application side at least http://geekswithblogs.net/jeroenb/archive/2011/12/14/signalr-starter-application.aspx

Mark M
  • 1