- Thread starter
- #71
Thanks Morph! It's basically the same for me. Sometimes I feel that I have missed at least 20 years of progress in web technology, but then I realize that e.g. the Katana project wasn't started too long ago. I think that this is mainly because MS finally realized two things:
As a reminder to myself - Here we have an example how to implement my "virtual file system" (i.e. extendable by MP2 plugins and taking care of different client types) directly in Owin/Katana:
http://www.choudeshell.com/blog/extending-katana-for-fun-and-profit/
https://gist.github.com/choudeshell/5174495
This btw can also be used to expose our MP2 Resource Provider system to a http server and later on replace our existing http server. I haven't had a look into serving UPnP with it, but I'm sure it's not too hard to do...
They really implemented a lot of possibilities in Owin/Katana already and it is really fun to see how easy it is to use and extend it. If you need an additional technology, it's just a single line of code to add it to your web app. You need a simple static file web server? app.UseStaticFiles() - that's it. You need authentication support via a login form? app.UseFormsAuthentication() - same goes for compression and even complete frameworks like ASP.Net MVC, ASP.Net WebAPI, SignalR etc. If you need it, just one line of code to add it.
The only downside is that it takes a lot of reading to understand the possibilities and as mentioned, the documentation is not always good.
But it's fun, so I will definitely continue
- To keep track with new web technologies in time MS itself is too big and too slow. That seems to be the reason why they e.g. decoupled the development of WebAPI from the development of .net. The release cycle of .net is just too slow and providing NuGet packages instead makes it possible to deliver updates with new features much quicker.
- The open source community has so many ideas that MS can take advantage of it. That seems to be the reason why they opensourced the asp.net webstack and just make sure that the code quality is high enough by reserving write access to the repo to MS employees while letting the community make pull request for improvements and new features.
As a reminder to myself - Here we have an example how to implement my "virtual file system" (i.e. extendable by MP2 plugins and taking care of different client types) directly in Owin/Katana:
http://www.choudeshell.com/blog/extending-katana-for-fun-and-profit/
https://gist.github.com/choudeshell/5174495
This btw can also be used to expose our MP2 Resource Provider system to a http server and later on replace our existing http server. I haven't had a look into serving UPnP with it, but I'm sure it's not too hard to do...
They really implemented a lot of possibilities in Owin/Katana already and it is really fun to see how easy it is to use and extend it. If you need an additional technology, it's just a single line of code to add it to your web app. You need a simple static file web server? app.UseStaticFiles() - that's it. You need authentication support via a login form? app.UseFormsAuthentication() - same goes for compression and even complete frameworks like ASP.Net MVC, ASP.Net WebAPI, SignalR etc. If you need it, just one line of code to add it.
The only downside is that it takes a lot of reading to understand the possibilities and as mentioned, the documentation is not always good.
But it's fun, so I will definitely continue