Liste des Groupes | Revenir à cu shell |
The windows process API is crippled which is why threading is the mainThreading is the main method because of its performance in a tight coupled application. Crossing the process borders is very expensive.
parallel processing method in Windows and has been since 3.0.
If you thinkThere is no problem using socket select with Windows. Here is an implementation of a server doing that:
otherwise please give some examples. However I distincly remember trying to
port server to windows only to discover that sockets are some wierd
structure in windows instead of a simple file descriptor meaning it was
impossible to multiplex using poll() or select() on them, you had to have
a seperate thread to manage each connection. What a fucking mess designed
by idiots.
Objects managed by the OS.Historically UNIX started with singe fork() call. There was nothing butfork() copies the entire process space. No idea what you mean by "system
files, no system objects, nothing.
objects". Must be some windows thing.
It is not slow. Actually you can get same or better performance under Windows as under Linux. The problem is the default settings of the scheduling time interval. It is 10ms by default. Set it to 1ms and you will see the difference. Unfortunately 1ms is the hard limit. If you want it better, OK, there is VxWorks where you can go under 1ms.On the other hand, Windows NT was developed by people influenced withWindows NT was a slow unreliable dog.
the VMS design. VMS had a very elaborated process communication API. So
Windows inherited much of that, but must importantly the concept of
system resources managed by the OS.
Les messages affichés proviennent d'usenet.