When I do this:
s = new Socket(AddressFamily.InterNetwork, SocketType.Dgram, ProtocolType.Udp);
s.SetSocketOption(SocketOptionLevel.Socket, SocketOptionName.ReuseAddress,
true);
this happens:
** (NetDump.exe:25323): WARNING **: Missing member SetSocketOption in type
Socket, assembly /usr/lib/
Jonathan Pryor wrote:
This was done under .NET, but I doubt that mono is significantly
different for relative performance:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dncscol/html/csharp02172004.asp
http://blogs.msdn.com/ericgu/archive/2004/03/02/83053.aspx
http://gglaze.hom
Ben Maurer wrote:
On Fri, 2006-01-27 at 08:50 -0500, Chad Robinson wrote:
I have a question about Mono internals (or CLR internals?). How is
MethodInfo.Invoke actually implemented? I'm trying to write an extensible
application that would support loading custom modules in external
I have a question about Mono internals (or CLR internals?). How is
MethodInfo.Invoke actually implemented? I'm trying to write an extensible
application that would support loading custom modules in external DLLs.
However, the application is also tightly performance constrained. I guess what
I'm
I've read some tidbits, news articles, and blog posts about various
service-level options in Mono, but I'd like some feedback from some
users/developers - has anybody developed any services with long run times? I
have an application I'm rewriting that typically needs to run for 10-15 hours
at a
This is my first foray into Mono (and C#), and I'm impressed. The developers
have done a wonderful job getting things running. I'm sorry if this question
seems lame or has come up before, but I haven't seen it addressed yet;
hopefully somebody can give me some insight.
I have Mono deployed on a Li
