FAQ Superscribe Frequently Asked Questions
Q: What is Graph Based Routing?
A: Graph based routing is a route parsing strategy design for use in web applications. You can read the full explanation here
Q: How does Superscribe implement Graph Based Routing?
A: At it's core, Superscribe provides a fully compliant Graph Based Routing implementation written in C#. It also goes one step further than this, providing a DSL for creating definitions quickly and easily, as well as helpers for dealing with Owin pipelines and Asp.Net Web Api which are not part of Graph Based Routing itself.
Q: Why bother with a graph? What's wrong with a tree?
A: There's nothing wrong with a Tree, in fact the vast majority of routing cases will fit well with a Tree implementation. A Tree is still a type of graph however so these still work with no problems.
What the graph enables us to do is to provide multiple entry points into routes, reusing our definitions but enabling extra features. For example:
- /Api/Apps - regular route
- /Debug/Api/Apps - same route with tracing enabled
Q: Can I use Superscribe with Asp.Net MVC?
A: Not at present. We'll be looking into whether or not this is possible in the new year so stay tuned.
Q: Can I use Superscribe with Nancy FX?
A: At present you can use Owin routing to hand off from your middleware pipeline to Nancy but then Nancy's routing will take over. Work is under development to allow Nancy to re-use the results of Supersribes route parsing, so watch this space.