From ioS 7 onwards, there are newer ways for apps to run in background. Apple now recognizes that apps have to constantly download and process data constantly. Here is the new list of all the apps which can run in background. Apps that play audible content to the user while in the background, such as … Read more
Note: This post has been updated to include the JobScheduler API of the Android Lollipop release. The following is still a viable way, but can be considered deprecated if you’re targeting Android Lollipop and beyond. See the second half for the JobScheduler alternative. One way to do recurrent tasks is this: Create a class AlarmReceiver … Read more
Well, you can use “ignore_user_abort(true)” So the script will continue to work (keep an eye on script duration, perhaps add “set_time_limit(0)”) But a warning here: You will not be able to stop a script with these two lines: ignore_user_abort(true); set_time_limit(0); Except you can directly access the server and kill the process there! (Been there, done … Read more
See “Background Execution” section of the iPhoneAppProgrammingGuide. In short, your app must be one of these types: Apps that play audible content to the user while in the background, such as a music player app Apps that keep users informed of their location at all times, such as a navigation app Apps that support Voice … Read more
After a full day of testing, I can confirm that HealthKit background delivery does work in all of the following application states: background: in background and executing code, suspended: in background and not executing code, terminated: force-killed by the user or purged by the system. Keep in mind: part 1 Some HealthKit data types have … Read more
Yes you can detect a Call. but only if your app is running in the foreground. For this you can use the Core Telephony Framework. If your app will fall in any of the background running categories (VOIP, AUDIO, Location tracking or accessory ) you might be able to use the CTCallCenter in the background. … Read more
To start, I wouldn’t use JSP for this. There it is not for. When you’re on Java EE 5, use the container-provided jobscheduling APIs for this. Further detail depends on the container you’re using. JBoss AS 5 for example ships with Quartz out the box. Or when you’re using a framework on top of JSP/Servlet … Read more
You can accomplish what you want, but it is typically a bad idea. Several ASP.NET blog and CMS engines take this approach, because they want to be installable on a shared hosting system and not take a dependency on a windows service that needs to be installed. Typically they kick off a long running thread … Read more
Your problem is that you misunderstand the purpose of the servlet. It’s intented to act on HTTP requests, nothing more. You want just a background task which runs once on daily basis. EJB available? Use @Schedule If your environment happen to support EJB (i.e. a real Java EE server such as WildFly, JBoss, TomEE, Payara, … Read more
You need to save the PID of the background process at the time you start it: foo & FOO_PID=$! # do other stuff kill $FOO_PID You cannot use job control, since that is an interactive feature and tied to a controlling terminal. A script will not necessarily have a terminal attached at all so job … Read more