#ENUMERATING PRE INSTALL PACKAGES INSTALL#
#ENUMERATING PRE INSTALL PACKAGES UPDATE#
#ENUMERATING PRE INSTALL PACKAGES CODE#

Groups are not a security feature, itвЂ™s about message filtering. This of course means that any client can claim they are in a group and spy on your messages. SignalR stores enough state on the server to make groups work, but all groups that a client is a member of is round-tripped with that client. ThereвЂ™s tons of confusion about how groups work in SignalR and how it works in scaled out environments ( ). The JavaScript client checks for a keep alive ping from the server on a configurable interval and raises the вЂњconnection slowвЂќ event before it drops the connection and starts reconnecting. This feature allows clients to react to slow/buggy networks that drop connectivity often. In the second example, any connection to the hub as well as calls to Send require authorization, but calls to Send2 do not. The first example shows requires authorization for all connections to the hub and calls to any incoming methods. Now you can decorate your hubs or hub methods or both to get different granularities of security. Many of you wanted an easy way to mark a hub as requiring authorization and now you can do that by just specifying an attribute similar to MVC. The next feature on the list builds on the pipeline implementation. Each method takes the appropriate context so you can get whatever information you want about the incoming or outgoing invocation. The module has a bunch of different methods you can override, the above sample only shows 2 of them. HereвЂ™s an example of a hub pipeline module that logs all outgoing and incoming calls.

#ENUMERATING PRE INSTALL PACKAGES CODE#

You get to inject any piece of code anywhere in the hub pipeline for incoming and outgoing calls. Think of the hub pipeline like mvc filters but more powerful. This is the most powerful feature weвЂ™ve added in the new release. If you want to, you can remove this file and just add the call to your global asax with the rest of your route registration. There's even a little comment telling you what MapHubs does.

#ENUMERATING PRE INSTALL PACKAGES INSTALL#

When you install the new package, itвЂ™ll add a RegisterHubs.cs file to the project in the App_Start folder.

This is now an explicit call the developer has to make to enable this route. When using hubs, people always wondered how this magic ~/signalr/hubs url was getting registered. ThereвЂ™s obviously still some magic, just a bit less than before. Connected, Disconnected and ReconnectedД«efore we had these awful interfaces you had to implement to detect this, now itвЂ™s just an override on the Hub itself. The comments are pretty self explanatory but as part of this work we resolved this long standing feature request (itвЂ™s almost a year old!). This is a dump of all the new surface weвЂ™ve added for hubs. On the server side weвЂ™ve added quite a few new APIs for hubs after lots of feedback and discussion. As you already guessed, you can declare methods that the server calls on the client object and call methods that exist on the server with the server object. If they were called the same thing it just wouldnвЂ™t work so we decided to separate the namespaces. This came about because there was a subtle issue with naming methods on the client and server.

Hub API changesДЇirst thing to notice is the client and server members on the hub object.

#ENUMERATING PRE INSTALL PACKAGES UPDATE#

These will bring in the alpha1 packages but you can update them using NuGet to get the latest and greatest. When you install the ASP.NET 2012 Fall Update, youвЂ™ll see a few new things in your Add New Item menu. Install-Package вЂ“pre Visual Studio Integration If youвЂ™re using the package manager console, use the вЂ“pre flag to install it. If youвЂ™re using the NuGet dialog, pick the IncludePrerelease in the dropdown to see them. вЂ“ Service bus message bus implementation.

.Utils вЂ“ utilities for signalr ( signalr.exe).

вЂ“ Core server package with no host implementation.

There are new packages that you can use today in your applications. ThereвЂ™s also been lots of confusion about what to use, so IвЂ™m going to clear things up by enumerating the list of major changes. A lot has changed since 0.5.3 and there have been several people poking around trying to find out whatвЂ™s changed and whatвЂ™s new in the alpha. SignalR 1.0 alpha has been live for just over 2 weeks on NuGet, and a few seconds ago I just published alpha2. IвЂ™ve also given my first talk ever at Monkeyspace and then BUILD - both on SignalR. ItвЂ™s been a while since I last blogged as weвЂ™re super busy trying to make SignalR rock solid and 1.0 quality for you all to use.

Enumerating pre-install packages