"Nothing Destroys a Good Idea Faster Than a Mandatory Consensus" I've read both the Lifehacker article, and that to which it links; and I've now read all the comments, below it (as of this writing), and here's my thought (rolling around in my little pea brain like a BB in a tunafish can), for whatever it's worth...
I think that it all depends on the idea. I hear, loud and clear, all those who argue, below, that if it's the right group, sufficiently rightly thinking, then consensus can be good after all, and all that. But, honwestly, the more the idea departs from conventional wisdom, the less likely that consensus — virtually ANY consensus — could possibly be a good thing to get anywhere near it. The really creative, ground-breaking, why-didn't-someone-think-of-that-before kinds of ideas (which are also usually the ones which the most people think are silly and will never work) need to be conceived and then brought to fruition by those who have the self-confidence to do it despite what everyone else says...
Hope that helps. Gregg L. Napa, California USA. WS-Federated Authentication Module Overview. Windows Identity Foundation [Starting with the .NET Framework 4.5, Windows Identity Foundation (WIF) has been fully integrated into the .NET Framework. The version of WIF addressed by this topic, WIF 3.5, is deprecated and should only be used when developing against the .NET Framework 3.5 SP1 or the .NET Framework 4. For more information about WIF in the .NET Framework 4.5, also known as WIF 4.5, see the Windows Identity Foundation documentation in the .NET Framework 4.5 Development Guide.] Windows® Identity Foundation (WIF) includes support for federated authentication in ASP.NET applications through the WS-Federated Authentication Module (WS-FAM). Federated authentication allows a Security Token Service (STS) in one trust domain to provide authentication information to an STS in another trust domain when there is a trust relationship between the two domains.
A client in the Fabrikam trust domain sends a request to a Relying Party (RP) application in the Contoso trust domain. Working With the Entity Framework and the Web API « Perspectives on .NET Programming From Learning Tree International. In my last post, I talked about the new Web API controllers in MVC and showed how they work with simple data. In the real world, of course, I want them to work with my existing data, which uses Entity Framework. It turns out that this is far from straightforward (at least, in the beta). Let’s start by trying to expose some standard EF data. When I began coding my personal website www.cocktailsrus.com I used model-first rather than code-first development.
(At that point, my focus was on getting to know jQuery mobile, and I was not concerned with best practices in MVC; I have refactored it since). So let’s go back to basics and begin with an .edmx version of the simple data I used in my last post. The code to return this object using Entity Framework and Web API is as follows (with the result first placed into a variable so I can more easily examine the return in the debugger): When we try and access this in Internet Explorer, we get the following error message: Here are my types: Like this: .ajaxError. Description: Register a handler to be called when Ajax requests complete with an error. This is an Ajax Event. Whenever an Ajax request completes with an error, jQuery triggers the ajaxError event.
Any and all handlers that have been registered with the .ajaxError() method are executed at this time. Note: This handler is not called for cross-domain script and cross-domain JSONP requests. To observe this method in action, set up a basic Ajax load request. Attach the event handler to the document: Now, make an Ajax request using any jQuery method: When the user clicks the button and the Ajax request fails, because the requested file is missing, the log message is displayed.
As of jQuery 1.8, the .ajaxError() method should only be attached to document. All ajaxError handlers are invoked, regardless of what Ajax request was completed. How can I make a security token automatically expire in a passive STS setup? Upgrading TFS event subscriptions to 2010 SDK. Some days ago I started to upgrade one of my TFS customization to the 2010 SDK. The application I moved uses WCF to host its services and automatically subscribes and consumes TFS events.
It didn’t turn to be the easy, straight on upgrade I thought it should be. This is my findings during the upgrade. Relocated TFS SDK assembliesThe first (and about the only) thing I expected was to be replace TfsServer with TfsTeamProjectCollection, and in some cases TfsConfigurationServer. Moving my solution over to a new and clean machine with only VS2010 on it, I discovered that the Tfs SDK Assemblies has moved away from its old locations. After some searching I found the new location C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\ReferenceAssemblies\v2.0 Where did IEventService go ? Windows 7 securityWith all compiler errors fixed, it was time for a first test. TFS2010 switched to Soap1.2After some testing I don’t receive any incoming notifications. //NotifyServices.cs srvHost.Open(); OData and OAuth – protecting an OData Service using OAuth 2.0 - WCF Data Services Team Blog. In this post you will learn how to create an OData service that is protected using OAuth 2.0, which is the OData team’s official recommendation in these scenarios: Delegation: In a delegation scenario a third party (generally an application) is granted access to a user’s resources without the user disclosing their credentials (username and password) to the third party.
Federation: In a federation scenario a user’s credentials on one domain (perhaps their corporate network) implies access to resources on a resource domain (say a data provider). They key though is that the credentials used (if any) on the resource domain are not disclosed to the end users and the user never discloses their credentials to the resource domain either. So if your scenarios is one of the above or some slight variation we recommend that you use OAuth 2.0 to protect your service, it provides the utmost flexibility and power. As you can see this is a pretty simple model with just Users and Favorites. Business Rules.