What does "InputQueue" do in UDP example? And is it production ready? If not what are the alternatives?

Question

This is a question for the WCF team, for someone who knows the details of custom channels.
So i followed the udp example and built a custom listener and a replychannel for myself.
However I don't totally get what it's doing and how it's doing it. I'd like to ultimately put my code in production in the company i work for.
But i don't think I understand it enough to be able to do that.
The listener itself: not a biggy. The replychannel: not much code there. The encoder: a breeeze. Other custome behaviors: very understandable.
However, there is one thing and it's not a small thing. That's the InputQueue used in the custom replychannel (see udp example).
To me this looks like the brains of the operation (channel ops I mean). Yet it is not in the WCF framework itself. And there is no documentation on how to go about writing one from scratch either.
Since we don't have access to the source code of WCF either, say to see how HttpReplyChannel was written, the only hope we have is to use the InputQueue as is. So i'd like to know, possibly from whoever wrote it, that it is of a quality that the rest of the WCF is written to?

thanks
jeff

Answer 1

Are you facing any problem with the InputQueue In the sample?

---

http://blogs.msdn.com/sajay

Answer 2

The source code to WCF (3.5 SP1) is now available via Microsoft Shared Source Initiative:
http://referencesource.microsoft.com/netframework.aspx

HTH,

 --larsw

---

Lars Wilhelmsen | Development Lead | KrediNor, Norway | Connected Systems MVP | http://larswilhelmsen.com/