|
|
|
|
|
|
|
<<
Page 1 of 2
>>
Inside the Standard Bindings: WSFederationHttp
Nicholas Allen
writes "The final HTTP binding that I'm covering in this series is WSFederationHttp. Federation is the ability to share identities across multiple systems for authentication and authorization. These identities could either be for users or machines. This binding is intended for the very specific scenario of federated security.
Standard disclaimer:
"
WCF and Security solutions
RHurlbut
writes "I mentioned previously I worked on some security work with WCF. In March, I worked with Sam's team to put together a first prototype of a WCF secure solution using Active Directory as well as research into WSFederationHttpBinding and Active Directory Federation Services (ADFS). Sam and crew have extended those initial ideas into a set of great solutions as he describes here , here, and here (Aaron's post). You owe yourself a look to see the great work they have done.
Keith Brown also announced the launch of the ..."
Inside the Standard Bindings: WSHttp
Nicholas Allen
writes "The WsHttp binding is a lot like the BasicHttp binding with the Web Services knob turned up a little higher. Where BasicHttp stops with message security, WsHttp continues with transactions, reliable messaging, and WS-Addressing either enabled by default or available through a single control setting. Otherwise, the HTTP-ness of the two bindings is the same and all of the binding elements being used have appeared in previous bindings....
"
Inside the Standard Bindings: NetNamedPipe
Nicholas Allen
writes "Part 3 of the series detailing the standard bindings (Part 1 was on BasicHttp and Part 2 was on NetTcp). The standard binding for named pipes is very similar to the standard binding for TCP. Named pipes are simpler because the WCF implementation is only meant for on-machine use and consequently there are fewer exposed features. The most notable difference is that the Security.Mode setting only offers the None and Transport options. SOAP security support is not an included option.
Standard disclaimer:
I've cut down on the number ...
"
Inside the Standard Bindings: NetTcp
Nicholas Allen
writes "Today continues the series I started last week about the standard bindings. The previous article covered the BasicHttp binding. Today's article covers the NetTcp binding, which is going to be the popular out-of-the-box choice for communicating over an Intranet. The default configuration for TCP is faster than the configuration for HTTP, but intended only for WCF-to-WCF communication. You can open that up with ..."
Inside the Standard Bindings: BasicHttp
Nicholas Allen
writes "Since there isn't a lot of documentation about how the standard bindings are put together, I decided to start a series going over each of the bindings and looking at their component pieces. I'm not going to dive into all of the binding elements so that the presentation goes a little bit faster. I'll probably get back to that some time this summer and do another series that focuses on individual binding elements.
The BasicHttp binding is going to be one of..."
Atlas and WCF
Marc Mercuri
writes "We actually released a CTP of Atlas back in March, and it actually came with a Go Live license so you both develop with it and put it into production.
I wanted to make sure you were aware of the WCF/Atlas sample code that was out there. If you're used to WCF, it's a great first step on the road to building some really interesting AJAX-style apps.
You can find the sample here. If you don't have Atlas installed yet, this site will be helpful.
"
Creating Custom Bindings
Nicholas Allen
writes "A CustomBinding defines a binding by providing a thin wrapper around a collection of binding elements. Custom bindings don't have any of the niceities of a handcrafted binding, such as properties that provide direct control over the binding elements and their settings. However, in return, a custom binding is very cheap to create and doesn't require defining a new class.
The bulk of the methods for the CustomBinding class deal with importing the ...
"
Breaking Changes for WCF and Infocard
Marc Mercuri
writes "So now that you've got the new bits, the next question is - “What's changed?”
The list of breaking changes for WCF and Infocard have been posted here.
"
Introducing IDefaultCommunicationTimeouts
Nicholas Allen
writes "Today's post is a light entrée covering the IDefaultCommunicationTimeouts interface. This interface bundles up the standard group of timeouts- open, close, receive, and send- into one convenient package. A surprising number of classes implement or consume IDefaultCommunicationTimeouts, usually resulting in a series of several delegations in order to reach where the timeouts are actually set...
"
Using the BufferManager
Nicholas Allen
writes "A BufferManager recycles the byte buffers used when reading and writing buffered messages. There's some allocation overhead creating these frequently used buffers, making buffer recycling a net win in high-throughput scenarios. As you move to larger message sizes though, buffer recycling becomes less of a factor and then eventually a net loss. All of this is encoded in the BufferManager class so that you don't have to think about it.
When you create a BufferManager, you specify...
"
Tracing in WCF
Marc Mercuri
writes "If you know me, you know I hate re-creating the wheel, so I did a quick search to see if this information was already documented. As fate would have it, Madhu Ponduru literally just put together a good post on the subject.
If you haven't tried tracing yet, you definately should.
Check it out here:
"
New article on WCF instance management techniques
Marc Mercuri
writes "If you're not familair with Juval Lowy, he's one of our Regional Directors and writes some great content that you can find in a number of areas (including MSDN online and in print).
He's just released an article on WCF instance management techniques - check it out here.
"
Migrating Remoting to WCF
Marc Mercuri
writes "Ingo Rammer just posted an article on migrating Remoting to WCF. It's good stuff - if you're doing remoting today, you should read this.
Find it here:
"
Building A Custom Message Encoder to Record Throughput, Part 3
Nicholas Allen
writes "After a short break we're back to working on the custom message encoder. The complete source code for the encoder is available in Part 1 and Part 2 of this series. Today and tomorrow I'll be performing some runs using the encoder to show how it works. We'll need a sample client and server application to host the encoder. I've dusted off the code I put together for the FileTransport to fill this role... "
Understanding HTTP Authentication Support in WCF
Nicholas Allen
writes "...The initial request from a client is typically an anonymous request, not containing any authentication information. HTTP server applications can deny the anonymous request while indicating that authentication is required. The server application sends WWW-Authentication headers to indicate the supported types of authentication scheme. This document describes several authentication schemes for HTTP and discusses their support in Windows Communication Foundation (WCF)... "
WCF serialization rules
Aaron Skonnard
writes "I recently wrote an article on the various serialization options in WCF (which will soon be published in MSDN Magazine). It focuses on the differences between XmlSerializer, DataContractSerializer (DCS), and NetDataContractSerializer, their programming models, tool support, and when to use one vs. the other...."
WCF DataContract DataTypes
Mitchell Land
writes "Awesome (and short) post by Sowmy Srinivasan on the serialization model in WCF (formerly known as "Indigo")."
Upcoming WCF training offerings
Aaron Skonnard
writes " few weeks ago we asked about interest in WCF training locations. We've scheduled a few prominent locations on the West/East coasts and will likely schedule a few more in other requested locations..."
Building A Custom Message Encoder to Record Throughput, Part 1
Nicholas Allen
writes "Now that we've seen how to write a custom transport, I thought I'd tackle another common request, which is to write a custom message encoder. A message encoder serializes an instance of the Message class into bytes. This is generally a much simpler operation than actually sending those bytes to someone, so we'll be able to get through the message encoder sample much faster than the transport sample... "
<<
Page 1 of 2
>>
|
|
|
|
|
|
s
|
|
|