Date | Commit message (Collapse) |
|
SleepyPenguin::Epoll#delete method added for "soft" failures
Documentation updates and cleanups, the website is now
JavaScript-free!
(Ignore the 1.1.0 "release", it was a lie)
|
|
Ugh, release got fat-fingered :<
|
|
SleepyPenguin::Epoll#delete method added for "soft" failures
Documentation updates and cleanups, the website is now
JavaScript-free!
|
|
No need to burden applications.
|
|
Switch documentation over to wrongdoc, no more JavaScript!
Our documentation still sucks.
|
|
|
|
We do not depend on external libraries other than the
system C library
|
|
It seems to make more sense this way... Editors wanted :)
|
|
Should be ready for release
|
|
Some of the GC tests aren't realistic, but if they work in MRI
then we can expect them to work reasonably well everywhere.
|
|
Rubinius 1.1.1 does not include this function
ref: http://github.com/evanphx/rubinius/issues/497
|
|
Tested on Rubinius.
|
|
We shall release without SignalFD support
|
|
This wraps the eventfd(2) interface of Linux. Like TimerFD, it
is not available on older distributions.
|
|
This wraps the timerfd_* interface in the Linux kernel.
It is not available on older distributions.
|
|
This can potentially be very powerful under 1.9
with native threads
|
|
It was just st.h in the old days.
|
|
There can be ways (in the future) where supporting
Epoll#dup/Epoll#clone can proveuseful, so continue to
support them until proven otherwise.
|
|
There are no FD flags besides FD_CLOEXEC, so
there's no point in making an extra fcntl()
call.
|
|
It's dangerous to preserve epoll descriptors across fork,
especially in Ruby where the GC can invalidate objects at any
time. Installing pthread_atfork hooks prevents VALUE references
stored in the kernel from leaking across process boundaries,
making it far more difficult for a sanely written application to
leak invalid VALUEs to the user.
|
|
We don't have to emulate the C API exactly, and it
makes life saner/easier for our users.
|
|
Storing Ruby object values in the kernel means
they won't be visible to the GC, but for the
most part it's safe.
|
|
Just to make sure edge-triggering works on newly
created TCP connections.
|
|
|
|
|
|
|