Skip to content
This repository has been archived by the owner on Jan 24, 2021. It is now read-only.

v2 Requirements #2160

Closed
2 of 4 tasks
jchannon opened this issue Dec 10, 2015 · 7 comments
Closed
2 of 4 tasks

v2 Requirements #2160

jchannon opened this issue Dec 10, 2015 · 7 comments
Milestone

Comments

@jchannon
Copy link
Member

As @thecodejunkie has put in his blog we have plans for v2 and we need to document what we want and need to achieve this goal. This will then lead onto CoreCLR #1959 compatibility

NEED!

@dorvan
Copy link

dorvan commented Dec 12, 2015

what about an internal deadlock fencing algorithm?

@khellang
Copy link
Member

what about an internal deadlock fencing algorithm?

What does this even mean? 😕

@thecodejunkie
Copy link
Member

I think this is a bit of a moving target which depends on the number of hours we get to put in. A couple of things that pops into mind are

  • Swap out the default JSON serializer [WIP] Simple json spike #2163
  • Overhaul model-binding (there are some kinks in here and I'd like to cache reflection stuff to boost performance)
  • Look at providing a new route declaration syntax
  • Implement something like IModuleEnricher concept to give you better control about instantiating various NancyModule implementations
  • More documentations, samples, guides
  • Look at @khellang 's spike for a new boostrapper
  • Overhaul registrations (IApplicationRegistrations, IRequestRegistrations etc)
  • TinyIoC changes (child container + PCL) that @grumpydev has flagged
  • Improve the Diagnostics Dashboard (new UI + more info in there)
  • Rewrite tracing

There are some of the things that I've had on my radar for a long time and a lot of them should go into a new major, instead of a minor

@simosentissi
Copy link

are we thinking of keeping the documentation in github wiki? I am thinking readthedocs or readme.io would be of good UX benefits especially that the content can be driven from the same source as now ?

@phillip-haydon
Copy link
Member

We have no plans to move the documentation from the wiki. I personally don't see any reason to move away from it.

@thecodejunkie thecodejunkie added this to the 2.0 milestone Jan 17, 2016
@jchannon
Copy link
Member Author

Should this be closed or updated?

@thecodejunkie
Copy link
Member

😜

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants