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, 13:16:00
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vdgp60$2nh73$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
User-Agent : slrn/0.9.8.1 (VMS/Multinet)
On 2024-09-30, Arne Vajhøj <
arne@vajhoej.dk> wrote:
On 9/30/2024 9:36 PM, Lawrence D'Oliveiro wrote:
On Mon, 30 Sep 2024 20:48:53 -0400, Arne Vajhøj wrote:
The world is moving from forking processes to starting threads.
That was tried in the 1990s -- threads for everything, even multithreaded
GUIs. It was soon discovered that was not a great idea.
>
Practically all GUI's are multi-threaded.
>
No. The GUIs I know of (GTK, Android, etc) are all single threaded and any
other threads which need to use the GUI need to queue a request on the GUI
thread.
For example, in Android, you can define a Handler on the GUI thread which
receives messages from other threads:
https://developer.android.com/reference/android/os/HandlerI tend to use:
https://developer.android.com/reference/android/os/Handler#sendMessage(android.os.Message)
to send messages from the other threads to the GUI thread.
At least a main thread and an event thread.
>
No. In the GUIs I am aware of, the main GUI thread _is_ the event thread.
Simon.
-- Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFPWalking destinations on a map are further away than they appear.