[Mono-devel-list] XSP && Win32
danielmorgan at verizon.net
Sat Jan 24 12:49:23 EST 2004
Take a look at NamedPipeStream.cs in
for using Named Pipes on Windows.
From: mono-devel-list-admin at lists.ximian.com
[mailto:mono-devel-list-admin at lists.ximian.com]On Behalf Of Gonzalo
Sent: Saturday, January 24, 2004 5:40 AM
To: Mono Development
Subject: Re: [Mono-devel-list] XSP && Win32
El sáb, 24-01-2004 a las 01:07, Christian Birkl escribió:
> Hi all,
> XSP as mod-mono-server doesn't currently support Windows and Apache due
> to the lack of unix sockets on this platform (see bug
> http://bugzilla.ximian.com/show_bug.cgi?id=52763). I don't think it is
> fixed since mod_mono (at least the cvs version) still uses unix sockets
> so i thought of a platform independend version w/o modifing too much of
> both code bases (xsp and mod_mono).
> Solution #1:
> Why not use plain tcp/ip sockets bound on local loopback
> (127.0.0.1) and a user port (> 1024)? This way we don't depend on unix
> operating systems and still can get xsp and apache2 with just a small
> lines of code changes to run on both platforms.
This is one of the options I'm pondering.
> Solution #2:
> The use of named pipes on win32 systems, but i guess they aren't
> supported by the .net runtime (tho one could use [DllImport] and
> CreateNamedPipe calls to kernel32.dll and write a simple NamedPipeSocket
> : Socket class. Changes in mod_mono.c wouldn't be so hard too since we'd
> just have to #ifdef some lines.
This is the one I'd like to implement, but I have not tested yet if MS
runtime has support for named pipes (using something like our
Mono.Posix/UnixEndPoint.cs). If it does, I'd prefer this option.
Mono-devel-list mailing list
Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list