The last development version is ngwsx-0.1.3, based on nginx-0.7.14.
Installation package: ngwsx-0.1.3-bin.zip, ngwsx-0.1.3-bin.rar.
Source package: ngwsx-0.1.3-src.zip, ngwsx-0.1.3-src.rar.
The sources are licensed under 2-clause BSD-like license.
The last development version is ngwsx-0.1.3, based on nginx-0.7.14.
Installation package: ngwsx-0.1.3-bin.zip, ngwsx-0.1.3-bin.rar.
Source package: ngwsx-0.1.3-src.zip, ngwsx-0.1.3-src.rar.
The sources are licensed under 2-clause BSD-like license.
On Sun, Sep 07, 2008 at 10:07:39AM +0200, Hq He wrote:
The ngwsx still has much problems.
TODO of ngwsx: 1.IO Completion Port.
2.TransmitFile and TransmitPackets.
3.AcceptEx, ConnectEx and DisconnectEx.
3.Multi-Thread.
The IOCP, TransmitFile, and AcceptEx support is already in my non-public
win32 sources. The main problem actually is multi-threads support (it
affects on all nginx sources) and win32 process model - I prefer to
use master/worker model, but not a single process. Also build
configuration
is another problem.
But the biggest win32 problem is support:
I do not use win32 at all, so it will be difficult for me to debug
it.
win32 has no coredump concept, this complicates debugging.
I do not want to reply many stupid questions of windows users,
many of them will not have any relation to nginx at all.
The IOCP, TransmitFile, and AcceptEx support is already in my non-public
win32 sources. The main problem actually is multi-threads support (it
affects on all nginx sources) and win32 process model - I prefer to
use master/worker model, but not a single process. Also build configuration
is another problem.
Do you know that, in theory, it is possible to implement COW fork in
Windows NT, using NT API (NtCreateProcess)?
Unfortunately this API is not public, but it is used by Microsoft to
implement their Win32, Posix and OS/2 subsystems.
But the biggest win32 problem is support:
I do not use win32 at all, so it will be difficult for me to debug it.
This is easily solved if there is a separate maintainer of the win32
port.
win32 has no coredump concept, this complicates debugging.
I do not want to reply many stupid questions of windows users,
many of them will not have any relation to nginx at all.
Again, this can be done by the win32 port maintainer, on a separate
mailing list.
On Sun, Sep 07, 2008 at 11:00:44AM +0200, Manlio P. wrote:
The IOCP, TransmitFile, and AcceptEx support is already in my non-public
win32 sources. The main problem actually is multi-threads support (it
affects on all nginx sources) and win32 process model - I prefer to
use master/worker model, but not a single process. Also build configuration
is another problem.
Do you know that, in theory, it is possible to implement COW fork in
Windows NT, using NT API (NtCreateProcess)?
Unfortunately this API is not public, but it is used by Microsoft to
implement their Win32, Posix and OS/2 subsystems.
Yes, I know, but even usual CreateProcess allows to run master/workers,
however, all workers will process configuration by itself.
----- Original Message -----
From: “Igor S.” [email protected]
To: [email protected]
Sent: Sunday, September 7, 2008 2:42:49 PM GMT +05:30 Chennai, Kolkata,
Mumbai, New Delhi
Subject: Re: ngwsx is a port of the nginx on windows platform.
On Sun, Sep 07, 2008 at 02:10:22AM -0700, mike wrote: