Actually its worse than that. We have found that *anything that uses
callbacks* suffers from the same problems (eg any async API, say a
timer).
We have looked at writing our own socket library but the scope of
these bugs is amazing.
On Thu, Aug 9, 2012 at 9:00 AM, gelin yan wrote:
>
>
> On Thu,
On Thu, Aug 9, 2012 at 1:47 PM, Greg Young wrote:
> 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 be
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
Or NHibernate, which is working on Mono.
/Oskar
2012/8/7 Jonathan Pryor
> Unless you _really_ need a System.Data.Linq-compatible API, I would
> suggest giving up. Instead, focus on getting the open-source EF release
> working on Mono, and use that instead.
>
> http://entityframework.co
