Changed io::read/write to not use a loop and return a count of successfu...

[rrichardson]

changed io::read/write to not use a loop and also return a uint of the count that they wrote or read.
added reregister and register_opt functions to event_loop and the pollers that it uses.
moved event_loop::connect into net::

[carllerche]

Looks good, missing kqueue support ATM though. I could take a stab at it when I have a moment.

[markuskobler]

Should this not be event::EDGE instead of event::LEVEL?
Seems to cause the event loop to constantly wake up otherwise (on linux atleast)

[rrichardson]

You're right. This would be a good case for EDGE without ONESHOT, since
we're just waiting for the poll on the fd to timeout anyways.

On Tue, Nov 25, 2014 at 8:47 AM, Markus Kobler notifications@github.com
wrote:

In src/event_loop.rs:

@@ -74,7 +73,7 @@ impl<T, M: Send> EventLoop<T, M> {
let notify = try!(Notify::with_capacity(config.notify_capacity));

     // Register the notification wakeup FD with the IO poller

•    try!(poll.register(&notify, NOTIFY));
  

•    try!(poll.register(&notify, NOTIFY, event::READABLE | event::WRITABLE, event::LEVEL));
  

Should this not be event::EDGE instead of event::LEVEL?
Seems to cause the event loop to constantly wake up otherwise (on linux
atleast)

—
Reply to this email directly or view it on GitHub
https://github.com/carllerche/mio/pull/57/files#r20862879.

“Science is the great antidote to the poison of enthusiasm and
superstition.” -- Adam Smith

[carllerche]

I am currently working on getting this PR to work with kqueue

[carllerche]

Resolved by 0122914