The Description Tree Heirarchy

One of the things we didn’t get a chance to write as much about as we wanted to by RTM — but will fix soon — is the description tree. The service-side description tree consists of the heirarchy of objects starting with ServiceDescription class. The client-side description tree heirarchy starts from the ServiceEndpoint class. Uh-oh: The…

1

Sessionless Duplex Services, Part Two: Lifetimes and Contexts

Two posts ago I wrote the following post about how to build a duplex service and client that does NOT use sessions. Once I wrote the sample, I wanted to extend it to provide some more flexibility. I’ve done that now, but in so doing, I ran across some issues that make this type of…

0

Quick WCF Metadata Publication Walkthrough

I’ve been having a conversation with Scott Klein, who is busy writing a book on WCF (http://www.amazon.com/Professional-WCF-Pr%20ogramming-Development-Communication/dp/0470089849/sr=1-2/qid=1161195651/ref=sr_1_2/102-4898838-8936%20108?ie=UTF8&s=books). He’d been reading and following the documentation about publishing service metadata and had figured out how to do this in code, but for some reason he just didn’t understand the errors resulting from his attempt to use the…

4

Sessionless duplex services? No problem. Small issues, yes; problems, no.

Duplex is neato, definitely, because among other things it allows a service to push information at clients as it sees fit. You could just have two services, and one service throws an endpoint at the other and then listens for stuff coming back, too, but there are scenarios for this and scenarios for that. Sometimes…

4

Last note on the return of WCF client objects.

It would best be said, in the end, that a client object returns from an operation call (including a one-way operation) when the outbound message is sent by the transport. This can be a network call, but need not be. The most obvious example is handing the message off to a message queue. Sigh. I…

0