My Product / Idea Backlog
This post is a work in progress. I feel that I need a place to organize all my pet projects, whether they still only exist in my head or have materialized into some code.
-
Miles Platform
- Active Directory FOAF Gateway – internal beta
- Active Directory Photo Uploader – internal beta
- MOAT (Meaning Of A Tag) service / client – idea
- Internal Library service / client – prototype
-
WCF related
- ChunkingChannelEx – bug fixing
- XMPP Transport Channel – research/inception stage.
- WCF Test Client Extended!
-
Miscellaneous
- Agressive – Silverlight-based, lightweight Time Management System – planning/prototyping stage.
- Visual Studio Theme Explorer – planning phase.
- Tinyject – A tiny IoC/DI container in about 200 lines of C#.
The idea is to release as many of these under a liberal open license – probably hosted on CodePlex or a similar service.
Comments
Comment from larsw
Time January 29, 2009 at 8:27 pm
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
Comment from jcdekoning
Time January 29, 2009 at 7:17 pm
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?