molo_

Gandi.net. Some people say their support is mediocre, but I haven't had to use it. Good luck.

-molo

You can proxy https. See RFC2817 section 5.

-molo

Sure, that wasn't directed at you personally. Thanks and cheers.

Well it seems that we hit the nesting limit, so I will reply to this post. I'm not including a URL, I'm just signing my name. Please keep in mind that is a guideline.

Is it really necessary to downmod me for that?

Hi, thanks but that is what I've been doing for ages.

You argue for more control, but tying windows to threads at the OS layer is actually enforcing less control.

This is about an OS-layer API, not a windowing toolkit API. Tying the window to a thread at this layer makes it impossible to have a single-threaded UI application. It is inflexible.

This is more than just a quirk. Lets go through the bogons here:

1. Signal system confuses notifications with commands

2. API ties windows to threads

3. System allows you to send WM_DESTROY from one thread to another even though it provides undefined behavior

4. DestroyWindow() can only be called from a particular thread (related to item #2)

5. The API doesn't detect that the window has been destroyed as far as the application is concerned (whatever happens in ForgetWorkerThread() or PostQuitMessage(), the window actually goes away) without a DestroyWindow() call.

In short, WTF.

[edit: format]

Wow, thanks for exposing me to how braindamaged win32 really is.

In North America there seem to be two seasons for apples: autumn in North America, and autumn in South America. In September and October you get the fresh NA apples. In March and April you get the fresh SA apples. There is no reason to have an apple older than 6 months.

This article could really do with some photographs. I don't think the local Whole Foods by us does some of these things.

Also, this fictional account appears in Wireless, a collection of short stories and novellas by Stross. It is great to see that medium still alive and publishable.

[Edit: format]

There are two contributions to the load factor: number of processes/threads on the ready-to-run queue and the number blocked on I/O. The processes blocked on I/O show up in the "D" state in ps and top and also contribute to this number.

This article entirely ignores the number of processes blocked on I/O. A load average exceeding the number of CPUs (cores, whatever) does not automatically mean the CPUs are overloaded.