Helios 2.0 manifesto
Aaronontheweb opened this issue · comments
Now that I'm not under as much insane deadline pressure as I was during the first year of Helios, it's time to go back and do things right.
Goals
Helios 2.0 will have the following goals:
- Helios will be easy to understand and use.
- Helios will be singularly focused on doing one thing well: writing reactive, networked applications in .NET 3.5 / 4.0 / 4.5.
- Helios will more closely follow the Netty project's architecture and design goals. It won't ever match 1:1 with Netty, but we will borrow from their years of experience and astonishing success in equivalent JVM applications.
- Helios will include full documentation and tutorials.
Roadmap
We intend to accomplish these goals in the following steps:
- Remove everything from Helios that is currently not used or not relevant to this roadmap. House-cleaning.
- Provide clear specs for how new moving parts are supposed to work under Helios 2.0 - i.e. how do I add a step in the request processing pipeline? and so forth.
- Redesign and re-implement existing functionality in order to support specs.
- Provide integration and access points for enterprise concerns, such as monitoring and logging.
@Aaronontheweb does 2.0 include the hook/ladder stuff we were discussing?
@skotzko point 4
Provide integration and access points for enterprise concerns, such as monitoring and logging.
@Aaronontheweb [facepalm] Doh. Must read gooder.