feature($http): parameter to avoid triggering $apply

[dragosrususv]

PROBLEM: Complex pooling fed screens become unresponsive when they have 4-5 poolers at 2-3 seconds each.

SOLUTION: allow the developer to trigger $apply via $timeout(f(), 0) and allow him to opt out of the $digest cycle on each $http request

PROPOSAL:
$http({...., apply: false}) // by default the $apply will be triggered; if false, it will not be triggered

I can make a PR - just wanted to get in sync with the community, if they reached this problem.
Please mind that I'm forced to consider ReactJS like frameworks due to this limitation.

[lgalfaso]

There are a few hurdles as $http uses $q extensively, but if the issues can be solved and the implementation is good, I see no problems.

BTW, do you know that there is $httpProvider#useApplyAsync that can partially solve this?

[Narretz]

Duplicate of #2049

I'd be happy to include this in a future release.

Here's a PR that attempted to do this:
#12557

There's also this issue, which should be considered when implementing this: #13108

[dragosrususv]

@Narretz thank you kindly - tried to search before but haven't found the other ticket. I'm glad that this is not new to our community and people are interested in keeping good performance in large angularjs apps.