The sooner we have a fix for the inject problem the better because we are not very satisfied with the current workaround (continuous call to timer.schedule with a 1 millisecond delay).
We might not be able to test any new big release before some time as our focus now is going to be on other areas of the messaging infrastructure(Dispatch Router mainly). However if the only way is by having the proactor based code then we will have to adapt for Solaris. Regards, Adel ________________________________ From: Alan Conway <[email protected]> Sent: Friday, January 6, 2017 11:40:42 PM To: [email protected] Subject: Re: [Proton 0.16.0] Is libuv mandatory to compile Proton? On Wed, 2017-01-04 at 09:36 +0000, Adel Boutros wrote: > Thank you Andrew for this clear explanation. > > > Epoll is not supported on Solaris. So we will have to think of an > alternative for this OS (poll which you suggested should work). > > > As for libuv, we are currently compiling Proton 0.16.0 without it > because we don't have bandwidth to check if libuv is working on > Solaris. I will have to discuss internally to see if we can allocate > some bandwidth to dealing with libuv on Solaris. If you have any > input at this level, we will highly appreciate it. > > > Alan Conway stated in another discussion that libuv should fix the > slowness we detected in the event injection API. I don't know if > poll/epoll would also address this issue which is a bit critical for > us. > To clarify - the event injection problem is not related to libuv specifically but is in code that is getting re-organized by the proactor IO rework so I was hoping to avoid fixing it twice. For solaris any of libuv, a native poll() proactor, or patching the injection problem directly in the old reactor-based code are possible resolutions. Ideally I'd prefer to bring solaris forward to proactor- based code that also solves the inject problem, but we may have to fix the inject problem in the old code first if that can't happen fast enough. Cheers, Alan. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
