-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade project to Nancy 2.0-barneyrubble #1
Comments
Side note: great project, I have an instance I put up last night that is very useful for some browsing, etc. I had built my own custom API/tool for this customer they use to upload images/videos into specific containers from their mobile app, so this was really cool to see (and I'd be interested how this scales at high usage). This mobile app slams my ASP.NET API pretty good but Nancy is just so much faster to respond, I wonder--I may have to benchmark, could switch the main API to Nancy :). |
Send a pull request? 😉 I am busy this week and all the time, but I would look at it at some point 😄 This was created two years ago and is just a simple demo, I never used this for anything. And I feel that the application is quite simple now, the REST GET calls are directly mapped to the Azure blob storage, there should probably be some kind of business layer/controller in between. |
Will do! Like I mentioned I'll also have to do some benchmark/stability testing--if I take it that extra step (adding biz logic, probably logging provider) I may swap out the asp.net 4.5.2 WebAPI that is currently there just to consume "multi-part/form" posts from these disparate mobile apps and save image/video to blob and then metadata -> database |
Upgrade project to use Nancy 2.0 style routes & host on Kestrel (and still Azure, optionally)
Didn't realize you couldn't file your own issues O_O lol
The text was updated successfully, but these errors were encountered: