Sujet : Re: Apache + mod_php performance
De : clubley (at) *nospam* remove_me.eisner.decus.org-Earth.UFP (Simon Clubley)
Groupes : comp.os.vmsDate : 01. Oct 2024, 18:52:59
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vdhctr$2qrst$1@dont-email.me>
References : 1 2
User-Agent : slrn/0.9.8.1 (VMS/Multinet)
On 2024-10-01, John Dallman <
jgd@cix.co.uk> wrote:
In article <vdgp60$2nh73$1@dont-email.me>,
clubley@remove_me.eisner.decus.org-Earth.UFP (Simon Clubley) wrote:
>
No. In the GUIs I am aware of, the main GUI thread _is_ the event
thread.
>
On at least Android and iOS, developers are warned that if the GUI thread
is unresponsive to events for more than a few seconds, the OS will assume
that it has hung or is infinite looping, and will start popping up
warnings and/or killing the application. The GUI thread is required to
start other threads to do anything that may take significant time.
>
Exactly. And at least on Android (I don't know about iOS), those new
threads have no direct access to the GUI, the GUI event queue, or its
widgets. They have to post a message to the GUI thread, or communicate
with the GUI thread in another way, and then let code running within
the GUI thread update the GUI on its behalf.
Note that the message queue mentioned above is NOT the GUI event queue.
It is a generic Android message queue facility which is nothing to do
with the GUI. Multiple threads can create their own message queues and
receive messages from other threads. The messages are processed by a
handler within the thread that is registered when the message queue is
created.
These OSes consider the GUI to be the main thing of an application. Since
they are very user-focused OSes, at least as much about emotional
gratification as computing, this makes some sense.
>
The vendors have also seriously lost the plot with the decisions they
are making with the new Android versions.
I've just had to move to a new Android phone due to the turning off of
3G here in the UK. I was very happy with my old phone even though it
was quite limited in resources compared to the current phones.
In particular, I could have multiple applications open in the background
at the same time without them getting killed. Now, on the new phones,
as soon as you let the screen power off, the background applications are
now killed within a couple of minutes and are killed in a way that doesn't
even allow them to save their state via the standard Android API. :-(
This happens even when you allow the applications to have unrestricted
battery usage and exclude them from memory cleaning. When you need a
website like the following, the phone vendors have lost the plot:
https://dontkillmyapp.com/Simon.
-- Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFPWalking destinations on a map are further away than they appear.