Re: Writing an OWIN-based application and running on Kayak

[Andy Selvig]

It only creates a dependency loop if you're trying to develop Kayak.Cli. ;) But maybe there are other good reasons to move the project. What are you're thoughts?

Yes, I suppose it isn't as much of an issue if you aren't working on Kayak.Cli, but the point remains. The way it's setup now, if you want to make a change to Kayak proper, you need to:

    Build Kayak -> Update Kayak reference in Gate.Kayak -> Build Gate.Kayak -> Update Gate.Kayak Reference in Kayak.Cli -> Build Kayak.Cli

If Gate.Kayak was a part of the Gate solution instead, it would be:

    Build Kaya -> Build Gate.Kayak -> Build Kayak.Cli

On a more conceptual level, it seems like the Gate solution should be at the top of the dependency hierarchy (not depending on anything else) since both sides of the coin (servers and frameworks) should be referring to it. If I were to write a new OWIN-compliant framework, I'd reference Gate and make my framework fit its interfaces. I wouldn't necessarily want to contribute to Gate just to get my framework to function.

In the end, I'm not really trying to stir things up too much, just throwing out thoughts. Perhaps the least disruptive solution is to simply move the Kayak.Cli project over into the Gate solution, since this would resolve the loop.