[Mono-dev] TCP Async

[Greg Young]

An update to this. Some of the failures have been taken away (also
with our patch mentioned). However simple test apps using sockets (or
it appears any callbacks) in mono are not stable.

This I would imagine prevent most from actually being able to use mono
for any serious work.

Greg

On Sun, Jul 22, 2012 at 7:20 AM, Gonzalo Paniagua Javier
<gonzalo.mono at gmail.com> wrote:
> On Tue, Jul 17, 2012 at 7:49 AM, Greg Young <gregoryyoung1 at gmail.com> wrote:
>> Hey all.
>>
>> As this is a big issue for us and I feel a huge problem for mono in general
>> at this point as it means sockets basically dont work which is a strong
>> point of unix environments, I would like to propose something I have done in
>> the past. I am willing to offer a bounty (personally) for a working fix to
>> this section of code of $500 usd (more if done quickly).
>>
>> Acceptance criteria is the included test working in a stable fashion in
>> Linux / bsd but just Linux is acceptable as well,
>
> Hi Greg.
>
> I have the test working with a tiny little change in mono master
> (applies cleanly to mono-2-10) *and* a change in your test code to
> avoid using ConcurrentQueue (I keep getting array index out of bounds
> here).
> The change to your test code is here: https://gist.github.com/3158357
>
> Last line before I interrupted the test (server):
> # Total connections: 100. Out:   3778.3kb/s  In:   3549.7kb.s  Pending
> Send: 0  In Send: 0  Pending Received: 0
>
> Last line before I interrupted the test (client):
> # Total connections: 100. Out:   3548.5kb/s  In:   3851.7kb.s  Pending
> Send: 10278  In Send: 45359  Pending Received: 0
>
> Can you make the payment through Paypal? :-)
>
> -Gonzalo



-- 
Le doute n'est pas une condition agréable, mais la certitude est absurde.