Check out the GitHub repo in my signature. It's very experimental at this time but the concept is there.
Also check out my project:
https://github.com/cornwarecjp/amiko-pay@blueadept:
Nice to see you made some progress too. Also nice to see we started at opposite ends of solving this problem, so there's probably a minimum of duplicated work. My Ripple-style network implementation allows for plugging in several different kinds of channel protection mechanisms, so it's probably possible to plug in your solution into my software.
How did you manage to make the channel securely bi-directional without transaction replacement? As the Wiki explains, the solution without transaction replacement is only secure in a single direction.