We added in 2.1 several lifecycle extensions to the ones already provided by Avalon: The request lifecycle, the global request lifecycle and parent aware.
While it seems to be possible to support the two request lifecycles in 2.2 (with fortress), I currently see no real way to support parent aware (but perhaps there is a way). However, I think we should avoid adding our own lifecycle interfaces whereever possible.
+1
So, let's think about them:
ParentAware ----------- Has been introduced to have a cleaner implementation for the selectors used in the sitemaps.
RequestLifecycle ---------------- I'm really thinking more and more that we simply should drop RequestLifecycle and GlobalRequestLifecycle.
So, I'm in favour of deprecating this in 2.1 now and removing it in 2.2.
WDYT?
+1
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin