ios - didReceiveMemoryWarning capabilities: how much could app do -

well, want know app 'capabilities' when app receives memory warnings.

- (void)applicationdidreceivememorywarning:(uiapplication *)application {     ddlogverbose(@"applicationdidreceivememorywarning");     [self executetasks]; } 

could bluetooth connections established? ( [central connectperipheral:perihperal options:nil] )
bluetooth peripherals scanned? ( scan started @ point )
kinds of background tasks executed?

my concerns:

i put establishconnections code in applicationdidreceivememorywarning handler. code tries establish connections peripherals known uids ([central connectperipheral:perihperal options:nil]). thought functionality restricted , app rejected.

upd:

am right core bluetooth long-time usage?

    - (void)applicationdidreceivememorywarning:(uiapplication *)application;      // try clean memory possible. next step terminate app 

so, if background service terminated, can put 'establish connections' code inside didreceivememorywarning preventing loosing connections. after system kills service , take care these connections 'events reviving service sleep when devices appear nearby'

there few questions in here. can answer first.

applicationdidreceivememorywarning looks , nothing more: message operating system free memory in short supply. can whatever want in response it, or nothing @ all. can allocate array of million ints if want.

but when operating system can no longer allocate app memory requires, app terminated. memory warnings nicety before occurs, , ideally can take action free memory.