add notes to keep track of longer term plans around custom responses,…

… blueprints config, and federation of additional core hooks

ROADMAP.md

@@ -162,16 +162,32 @@ Please also realize that the following notes may be slightly out of date from ti
   + Library of well-tested, well-documented, and officially supported modules for the most common everyday tasks in apps (e.g. password encryption)
 
 
-
 ## 1.1.0 and beyond
 
-+ **Expand `express-session`/Connect session store interface**
++ **Blueprint API: Support transactions, when possible.**
+  + See "FUTURE" comments throughout the code for the blueprints hook in this repo.
++ **Sessions: Expand `express-session`/Connect session store interface**
   + Expose a method in session stores which can be used to do an initial, asynchronous ping in order to check configuration.
   + Worst case, we should also be able to use [`.get()`](https://github.com/expressjs/session/blob/2667028d39b3655a45eb1f9579d7f66f26a6937f/README.md#storegetsid-callback) with a nonsense session id to do this-- the errors just won't be as nice, or as easy to negotiate.
   + The best middle-of-the-road solution is probably to get a couple of standardized error codes in the spec for `.get()`
     + Most likely, that's stuff like `ECONNREFUSED`
     + But would be a lot better if we could swing more specific error codes-- e.g. `E_BAD_SESSION_STORE_CONFIG` and `E_COULD_NOT_CONNECT_TO_SESSION_STORE`-- since that would eliminate the possibility of false positives due to throwing / `cb(err)`-ing.
 
+
+## 2.0.0 and beyond
+
++ **Custom responses: Deprecate res.ok() in favor of res.success(); as well as some other breaking changes to custom responses.**
+  + See first half of https://github.com/balderdashy/sails/commit/518bae84f01d17eac84c96977e5ed0c3b6a98083#commitcomment-20917978 for details.
++ **Blueprint API: Make the behavior of certain error conditions in blueprint actions customizable via `sails.config.blueprints.handle*`**
+  + See second half of https://github.com/balderdashy/sails/commit/518bae84f01d17eac84c96977e5ed0c3b6a98083#commitcomment-20917978 for details.
++ **Federate sails-hook-blueprints**
+  + In the process, pull the implementation of the three public RPS methods into sails-hook-sockets (and take the rest of the private methods out and drop them into the blueprints hook)
++ **Federate sails-hook-session**
+  + Remember: This will involve a few delicate tweaks to the boilerplate config generated by `sails new foo --without=session`
++ **Federate sails-hook-i18n**
+  + (Will need to publish the backwards-compatible i18n hook as a separate package at that point)
+
+