KennyW on the dreaded "null channel"

Don Box's Spoutlet

Syndication

Kenny's going to build an intra-AppDomain channel (http://kennyw.com/indigo/47).
 
Here's a thought - implement an XmlReader/Writer pair that simply constructs an in-memory linear sequence of data structures and smuggle the sequence across the service boundary as an implementation detail of the channel. 
 
No copying of strings.
 
No parsing of byte/char arrays to reconstitute the infoset.
 
If you needed to calculate a DSIG, you'd need to be much more clever of course.

Posted Oct 22 2005, 01:22 AM by don-box

Comments

Roman Kiss, MVP wrote re: KennyW on the dreaded "null channel"
on 10-22-2005 11:18 AM
Hi Don,

Few weeks ago I had a discussion about the null channel with Mike Vernal. I have built a dirty prototype of the NetNullBinding (I/O, Duplex and Transactional) for my Async Workflow model with 3 services such as Sync, Async and Error to encapsulate a business layer from the connectivity and have a one common workflow pattern for async (MSMQ) pre/post processing.

The concept of the Null Transport Channel is based on sharing an EndpointFilterTable of the all active IListener Channels created by NullListenerFactory and stored in the AppDomain Data Slot under the well known name.

In this scenario, the null transport will send (enqueue) a message direct to the queued input channel (without using an encoder/decoder).

I am planning to share my code and concept in my new article on the codeproject in next month.


Roman


Add a Comment

(required)  
(optional)
(required)  
Remember Me?