http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Interesting that you ran into the same InProcessMessageBus that I did. I have made a temporary fix available in this pull request: https://github.com/SignalR/SignalR/pull/559 Dfowler said he has a better idea for a permanent fix, but for now, the above PR should do :)http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment17http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment17Thu, 26 Jul 2012 16:09:42 GMTDamian, We do retries for thathttp://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment16http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment16Sat, 21 Jul 2012 08:02:23 GMTAyende, should be released if a few a weeks. Prob not in time for 1.2 though. I may scratch that itch then, for the craic. Fair enough on the other implementations... Still wondering if you handle dis/re-connects and any sort guaranteed message delivery in the case of a dropped connection? http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment15http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment15Sat, 21 Jul 2012 07:56:41 GMTDamian, That requires software that is not released, and I looked at the other WebSockets implememntations for 4.0. No thanks, they are scary inside. http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment14http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment14Sat, 21 Jul 2012 07:45:08 GMTDaniel, websockets are over the same https(s) ports. The initial connection is still http. IIS is not required. http://paulbatum.github.com/WebSocket-Samples/HttpListenerWebSocketEcho/ . Yes, this is .net 4.5, but there are other .net 4.0 websocket implementations out there.http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment13http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment13Sat, 21 Jul 2012 07:42:12 GMTSlava, We only need streaming one wayhttp://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment12http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment12Sat, 21 Jul 2012 07:32:30 GMTout f curiosity why not to use Bosh? xmpp were using it for very long time. http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment11http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment11Sat, 21 Jul 2012 00:11:29 GMTDamian, yes, in case you have a web server (starting with IIS 8) and a web application. This is just a database, that uses http as the transport protocol. Using websockets for this kind of thing would mean that we need additional ports to be opened on the RavenDB server, whereas long-polling can share the same connection.http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment10http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment10Fri, 20 Jul 2012 22:37:07 GMTDaniel, websockets would the be preferred mechanism to receive notifications, falling back to long polling if needed.http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment9http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment9Fri, 20 Jul 2012 20:14:33 GMTLet's setup some time to go over things. I'm sure it's something that can be solved pretty easily. That's the intent, there might have been some unrelated thing going on that was causing those issues.http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment8http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment8Fri, 20 Jul 2012 17:34:21 GMTDavid, I put Console.WriteLine in the disconnected, and it was getting called. http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment7http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment7Fri, 20 Jul 2012 17:25:23 GMTThe very first implementation looks like it should work just fine. We don't actually raise disconnect in the longpolling transport when messages are received. The logical connection hasn't been disconnected, just the underlying transport's connection (but that's what this abstraction is for). We buffer messages for 30 seconds, so if the transport is reconnecting it will still get those messages that it "missed" (as long as they are still there). If you didn't see that behavior I'd love to know why as it should just work.http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment6http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment6Fri, 20 Jul 2012 16:53:22 GMTSlava, if you don't have such fancy use-cases as Oren has, then go for SignalR. It is an awesome piece of software and we've been using it since its early version without any serious issues.http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment5http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment5Fri, 20 Jul 2012 16:47:30 GMTTobi and Damian, since RavenDB exposes only an http endpoint, I don't think it can nor should it use WebSockets or any other TCP based protocol except http. So, long-polling is probably the only way to go and it should work with any kind of http hardware, e.g. load-balancers (although the RavenDB client can do this much better).http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment4http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment4Fri, 20 Jul 2012 16:44:21 GMTThanks for sharing this, we are few days away from jumping into SignalIR, but now i would reconsider it. Did you try any other tools by chance, bosh, websockets? http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment3http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment3Fri, 20 Jul 2012 16:30:10 GMT> streamed endpoint This is over http, right? Does it handle re-connects? Is it proxy / firewall friendly? Any sort of guaranteed message (notification) delivery? Consider using websockets at all?http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment2http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment2Fri, 20 Jul 2012 12:57:01 GMTSounds like you don't need what SignalR has anyway: All you need is a persistent TCP connection to each listing client (of which there are only a few).http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment1http://ayende.com/157153/rant-signalr-crazyiness-head-butting-wall-crashing#comment1Fri, 20 Jul 2012 12:26:44 GMT