>
> I'm pretty sure IIS maintains some sort of message loop (I am not
> > sure how much this statement is correct - any Win* guru's [ Hi Aviram!
;-) ]
> > want to correct me? ). The choice of this kind of design for the program
is
> > inherit by the "choice" to use the Win* API. Apache designers suffered
no
> > such restraints.
>
> actually, this is the advantage of windows - you can have a message loop
> for non-GUI applications,
>
I missed most of the thread (if it wasn't for Gilad, I would have deleted it
entirely..) but just for the sake of completeness: A windows message loop is
*optional* I say again: OPTIONAL. Windows will create one for you, but you
don't have to use it in your app.
The fact that most (I might as well say 'all') windows applications actually
do use the message loop is because it has many advantages (such as the
example Guy gave before) and practically no disadvantages (since you can
ignore it altogether). I can write the application:
void main(void) {
printf("Hello World\n");
}
and compile it as a console application. I can write:
int WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine,
int nCmdShow) {
printf("Hello World\n");
}
and compile it as a Windows application (I can add MFC to it and have fun,
and *still* not use the message loop)
As you can see, there is no message loop in either of those apps.
-------------------------
Aviram Jenik
"Addicted to Chaos"
-------------------------
Today's quote:
We are all in the gutter, but some of us are looking at the stars.
- Oscar Wilde, "Lady Windermere's Fan", 1892
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
