[Mono-dev] TCP 3.0.1/2

[Rodrigo Kumpera]

Yes, it's the current suggested workaround until someone post a fix for the
epoll backend.


On Mon, Jan 21, 2013 at 10:10 AM, Roope Kangas <roope at grandcrugames.com>wrote:

> Hi!
>
> Whats the status of this issue?
>
> Is the "best" way on mono to implement a server by writing it against the
> *Async API and then settings MONO_DISABLE_AIO=1
>
> Seems odd?
>
> --
> Roope
>
> On Dec 7, 2012, at 6:44 PM, Rodrigo Kumpera <kumpera at gmail.com> wrote:
>
> By the way, did you guys tried MONO_DISABLE_AIO=1 by any chance on your
> tests? It solves the issue for me.
>
>
> On Thu, Dec 6, 2012 at 3:46 AM, Greg Young <gregoryyoung1 at gmail.com>wrote:
>
>> We have code that shows the issue
>> https://github.com/ysw/mono-socket-problem/tree/master/SocketTest
>>
>> Greg
>>
>> On Fri, Nov 30, 2012 at 4:10 PM, Rodrigo Kumpera <kumpera at gmail.com>wrote:
>>
>>> Btw, I managed to find a linux bot that shows the io callback issue.
>>> The TP test works fine though.
>>>
>>>
>>> On Fri, Nov 30, 2012 at 12:29 AM, Greg Young <gregoryyoung1 at gmail.com>wrote:
>>>
>>>> Thats already been provided (though its not hard to do). I will
>>>> reupload a test that shows beahviour.
>>>
>>>
>>>
>>
>>
>> --
>> Le doute n'est pas une condition agréable, mais la certitude est absurde.
>>
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20130121/2e58e7da/attachment.html>