On iOS, if we get a notification, and we want to run some CPU in response (eg an LSP sends us a notification that we have an HTLC pending), we have to fit within a relatively tight memory footprint and runtime. To do so, we'll probably want a specific mode/function for this - one that just loads up the ChannelManager and ChannelMonitors (that are live, not archived ones), doesn't load a network graph, doesn't sync the chain (or maybe only does if it fails some check that it last synced an hour or more ago? or a day ago?), and connects to peers, processes messages until things are quiet (do we need an LDK concept of "things are quiet") and then stops.
On iOS, if we get a notification, and we want to run some CPU in response (eg an LSP sends us a notification that we have an HTLC pending), we have to fit within a relatively tight memory footprint and runtime. To do so, we'll probably want a specific mode/function for this - one that just loads up the ChannelManager and ChannelMonitors (that are live, not archived ones), doesn't load a network graph, doesn't sync the chain (or maybe only does if it fails some check that it last synced an hour or more ago? or a day ago?), and connects to peers, processes messages until things are quiet (do we need an LDK concept of "things are quiet") and then stops.