Comments on: My Product / Idea Backlog http://www.larswilhelmsen.com/2008/10/01/my-product-idea-backlog/ Microsoft Connected Systems MVP Wed, 28 Jul 2010 23:39:23 +0000 hourly 1 http://wordpress.org/?v=3.0 By: larsw http://www.larswilhelmsen.com/2008/10/01/my-product-idea-backlog/comment-page-1/#comment-8 larsw Thu, 29 Jan 2009 20:27:10 +0000 http://larsw.wordpress.com/2008/10/01/my-product-idea-backlog/#comment-8 Hi jcdekoning, Your assertion is correct; netTcpBinding is for WCF WCF communication only over TCP sockets, using a proprietary, optimized framing protocol. My project is put on hold until someone comes up with a *decent* XMPP framework for .NET . All the ones I've checked out so far sucks - both in features and in design. Ideally I want a framework with support for the "XEP-0072: SOAP over XMPP" extension - or an easy way to add custom extension so that I can implement it myself. If that piece of the puzzle turns up, I will create a custom WCF transport channel and binding that wraps all the pieces nicely together. If you happen to know of a framework that suits my needs, please let me know. --larsw Hi jcdekoning,

Your assertion is correct; netTcpBinding is for WCF WCF communication only over TCP sockets, using a proprietary, optimized framing protocol.

My project is put on hold until someone comes up with a *decent* XMPP framework for .NET . All the ones I’ve checked out so far sucks – both in features and in design.

Ideally I want a framework with support for the “XEP-0072: SOAP over XMPP” extension – or an easy way to add custom extension so that I can implement it myself.

If that piece of the puzzle turns up, I will create a custom WCF transport channel and binding that wraps all the pieces nicely together.

If you happen to know of a framework that suits my needs, please let me know.

–larsw

]]> By: jcdekoning http://www.larswilhelmsen.com/2008/10/01/my-product-idea-backlog/comment-page-1/#comment-7 jcdekoning Thu, 29 Jan 2009 19:17:58 +0000 http://larsw.wordpress.com/2008/10/01/my-product-idea-backlog/#comment-7 Did you already get some results for your research project about creating an XMPP Transport Channel. XMPP is using a socket connection. But if i am right the netTcpBinding is not compatibly with normal .Net socket (or even other socket connections for example Java). Will this not result in developing special bindings on WCF which makes the implementation that huge that it is easier to keep it seperate from WCF? Did you already get some results for your research project about creating an XMPP Transport Channel.

XMPP is using a socket connection. But if i am right the netTcpBinding is not compatibly with normal .Net socket (or even other socket connections for example Java).

Will this not result in developing special bindings on WCF which makes the implementation that huge that it is easier to keep it seperate from WCF?

]]>