{"id":24704,"date":"2019-03-22T15:41:43","date_gmt":"2019-03-22T19:41:43","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=24704"},"modified":"2019-03-26T15:07:27","modified_gmt":"2019-03-26T19:07:27","slug":"late-responders","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2019\/03\/22\/late-responders\/","title":{"rendered":"Late Responders"},"content":{"rendered":"

Paulo Andrade<\/a>:<\/p>\n

\n

To summarize what was said above, some features that rely on the responder chain should be available even when the relevant responder isn’t on the the chain’s path.<\/p>\n

With that in mind I propose a solution I’m calling “Late Responders”. The way it works is that you setup a late responder registry further up the chain, such as the window. Then, the responders further down the chain can register a late responder with the registry and let it handle any features that should be always available.<\/p>\n

This way even if the responder itself isn’t in the chain’s path, its late responder surely will be.<\/p>\n<\/blockquote>\n\n

See also: Swift Diary #8: forwardInvocation<\/a>.<\/p>\n\n

Previously:<\/p>\n