[Mono-devel-list] mod_mono on osx / big endian systems.
bernard at ugsolutions.com
Wed Jun 9 16:42:10 EDT 2004
The "big endian" in the comment made me look at this not that I
use mod_mono but do use big endian machines.
Shouldn't this be a run-time check not a compile time one
so you don't need to rebuild DLLs. BitConverter.IsLittleEndian
can be used to test the endian-ness of the platform.
----- Original Message -----
From: "grompf" <grompf at sublimeintervention.com>
To: "Mono Development" <mono-devel-list at lists.ximian.com>
Sent: Wednesday, June 09, 2004 1:29 PM
Subject: [Mono-devel-list] mod_mono on osx / big endian systems.
> I've been debugging the usablilty of mod_mono on OSX with Apples Apache
> 1.3. Out of the box this doesn't work; when making a request
> mod_mono_server uses 100% cpu and locks. I tracked the problem down to
> BinaryReader.ReadInt32 assumes little endian on the stream; which for
> most of .Net is fine; however since mod_mono is native, and writing the
> in to the stream; this is wrong. Meaning that ReadString() in
> ModMonoRequest.cs is getting some insane size for the string to read.
> This patch solved the problem locally; but probably isn't ideal.
> This patch implements its own ReadInt32 which is different depending on
> wether BIGENDIAN is set or not...
More information about the Mono-devel-list