Hi,
Has anyone managed to use libevent in a Windows App Store app? From speaking to
Microsoft it looks like Windows App Store apps can use a subset of the Win32
apis. WinSock unfortunately is not in the allowed list of Win32 apis. Apps are
required to use the new Windows.Networking.Sockets api
So could a possible fix be to call event_base_once() with
callback==consider_read and timeout == 0 to make sure it gets processed in the
next iteration of the loop?
On Thursday, 22 December, 2011 at 8:57 PM, Mark Ellzey wrote:
> On Thu, Dec 22, 2011 at 01:33:28PM +0500, Haseeb Abdul Qa
What you guys mean when you say 'build correct infrastructure'? Does it mean
the ability to schedule callbacks and guarantee that callbacks will called in
the order they've been queued? For example a timer callback with a timeout of 0
is usually enough to enough to defer processing to the next i
Also, corresponding pull request: https://github.com/libevent/libevent/pull/2
Thanks.
On Tuesday, 20 December, 2011 at 3:34 AM, Haseeb Abdul Qadir wrote:
>
>
> Hi,
>
> I was investigating an issue with filtered openssl buffer events. The
> bufferevent stopped proces
Hi,
I was investigating an issue with filtered openssl buffer events. The
bufferevent stopped processing / pumping SSL data event when there was data
available in the underlying BE. This is a regression in 2.0.16 and I believe
the follow commit might have caused
it:https://github.com/libeven
