Just a playground for trying new things and seeing what I can break / fix.
I ultimately would like to use this as a basis for future projects, so I'm not planning on adding a bunch of features - just a core framework that I can easiliy base a new project on with minimal effort.
Currently, I'm seeing about a 100ms response time from the from azure to my browser. Not too shabby but I'd like to see if I could get it down even more. Network latency may not let me, though. Internally, I'm seeing about a 15ms running through the Visual Studio debugger.
Since angular caches the page templates locally and all we're doing is pulling json across the wire, page loads appear to be nearly instant.
The Nancy.Authentication.Toekn framework uses the filesystem to store the keyring for token generation / validation. I would like to move this to some type of key/value store like Redis. This way it will still persist to disk and be reboot safe, but it will reside in memory and be nice and fast. It also gives us the option of having a server farm setup that uses the same keyring.
- NancyFx based API
- Nancy.Authentication.Token for authentication
- Dapper.Net for a clean and fast ORM
- SQL Server based, though I'm looking at options for a document based data store. Maybe RavenDb or MongoDb.
- AngularJS / Bootstrap based web interface
- general code cleanup
- separate classes into individual files
- angular javascript stuff into individual files
- implement "features" structure in both api and web interface (http://the.fringe.ninja/blog/481/organizing-per-feature-in-nancy)
- implement a task runner to minify and concatenate the javascript files into one dist file (or something like that)
- javascript linter
- registration screen does not give feedback at all. Should automatically login and redirect.
- login page doesn't give feedback on bad password.
- add a logout option
- persist token to local cookie
- android version
- iphone version