Messaging Additions in Orcas

Messaging Additions in Orcas

  • Comments 6

I've had scattered posts in the past talking about the messaging features and enhancements in Orcas. Over the next few days I'm going to be doing a bit of consolidating to organize that information into a few listings of the top changes using reasonably sized chunks. Today I'll look at some of the new protocols and community-driven features that were added.

  • Remote client address. We've added capture of the address of the remote endpoint for TCP and HTTP connections so that you can act on the client address in your service code.
  • Custom password validator for HTTP. We've added support for attaching the existing UserNamePasswordValidator class that performs password-based authentication to the basic HTTP security system.
  • WS Addressing 1.0 Metadata. While the base addressing protocol provides a transport-independent way of describing the address of a service, metadata provides additional descriptive capabilities through WSDL and policy to specify how addresses should be used.
  • WS Policy 1.5. Policy is a description language for requirements and capabilities that is used to define a model for web service interaction.
  • WS Reliable Messaging 1.1. Reliable messaging provides a protocol for reliably transmitting messages between a pair of endpoints despite system or network failures.

Next time: Messaging Additions in Orcas, Part 2

  • How do I manually manage the context when sharing a client object? The default mode when using a context

  • Yesterday's big announcement was just a start. We have an even bigger one, hopefully today. Meanwhile

  • Hi Nicholas,

    I think you are the best source of WCF-related information. So probably if you don't know the answer, nobody knows :)

    I use new in 3.5 WCF classes for REST-based web services like this:

    var factory = new WebChannelFactory<MyInterface>(uri);

    var channel = factory.CreateChannel();

    Let have some cookie string or cookie container received via some other means. How to assign a cookie/cookie container to the channel?

    What I've found as a possible solution is havea wrapper class, that sets cookie using operation context in every method.

    However, this way looks somehow wrong to me. There is built-in automatic cookie handling, right? So there should be some way to get to internal cookie container, shouldn't it?

    Probably, we could you reflection to hack into WCF internals, but what is the easiest way in your professional opinion?

    Thank you in advance,

    Alexey

  • Hi Alexey,

    I did an earlier article on how to do manual cookie management.

    http://blogs.msdn.com/drnick/archive/2008/02/05/building-on-custom-cookie-handling.aspx

  • CLR/DLR/Popfly IronPython 2.0 Beta 2 Popfly Game Creator Windows PowerShell V2 CTP2 SOA/WCF Weekly SOA

  • Today wraps up the series on detailed messaging changes in Orcas. You can get the whole series here as

Page 1 of 1 (6 items)