about summary refs log tree commit homepage
DateCommit message (Collapse)
2010-01-09posix_mq 0.3.0 v0.3.0
This release adds a few new API methods, fixes MRI 1.8.6 support. We should now have full feature parity with underlying POSIX message queue C API. * POSIX_MQ#notify(&block) RDoc: http://bogomips.org/ruby_posix_mq/POSIX_MQ.html#M000001 This is only supported on platforms that implement SIGEV_THREAD with mq_notify(3) (tested with glibc + Linux). Other platforms will have to continue to rely on signal notifications via POSIX#notify=signal, or IO notifications in FreeBSD (and Linux). * POSIX_MQ#shift([buffer [,timeout]]) Shorthand for the common "POSIX_MQ#receive.first" when you do not care for priority of the received message. Rev, EventMachine and Reactor support are planned for Linux, FreeBSD and possibly any other platforms where POSIX message queues are implemented with a file descriptor.
2010-01-09MRI 1.8 does not have rb_str_flush
It's Rubinius-specific and we use rb_str_resize there anyways...
2010-01-08no point in non-blocking for fd notifications
It's not needed since the native thread will retry in the unlikely case of EINTR/EAGAIN. And writing one byte to a pipe that's guaranteed by POSIX to be at least 512 bytes is highly unlikely. It's also bad because F_SETFL takes the big kernel lock under Linux (and possibly other systems), and doing it unnecessarily is a waste of system cycles.
2010-01-08mode_t is usually unsigned
Most used open modes are well under INT_MAX, however
2010-01-07add POSIX_MQ#shift helper method
This acts like POSIX_MQ#receive but only returns the message without the priority.
2010-01-07POSIX_MQ#notify only works on GNU/Linux for now
SIGEV_THREAD is not easy to implement, so many platforms do not implement it.
2010-01-07POSIX_MQ#notify block execution on message received
This is implementation uses both a short-lived POSIX thread and a pre-spawned Ruby Thread in a manner that works properly under both Ruby 1.8 (green threads) and 1.9 (where Ruby Threads are POSIX threads). The short-lived POSIX thread will write a single "\0" byte to a pipe the Ruby Thread waits on. This operation is atomic on all platforms. Once the Ruby Thread is woken up from the pipe, it will execute th block given to it. This dual-thread implementation is inspired by the way glibc implements mq_notify(3) + SIGEV_THREAD under Linux where the kernel itself cannot directly spawn POSIX threads.
2010-01-02fix warnings on platforms where mqd_t != int
The POSIX manpages specify the return values of all mq_* functions besides mq_open(3) to be "int", not "mqd_t".
2010-01-02bump GIT-VERSION-GEN
Shouldn't affect most people since they should just take code from git...
2010-01-03posix_mq 0.2.0 v0.2.0
This release fixes notification (un)registration and should be fully-supported on modern FreeBSD (7.2+) releases. POSIX_MQ#notify=nil correctly unregister notification requests. POSIX_MQ#notify=false now provids the no-op SIGEV_NONE functionality. Under FreeBSD, using IO.select on POSIX_MQ objects is now possible as it has always been under Linux.
2010-01-02support POSIX_MQ#to_io under FreeBSD
FreeBSD implements an __mq_oshandle(mqd_t mqd) function to convert mqd_t to integer file descriptors.
2010-01-02fix build under FreeBSD 7.2
FreeBSD seems to need some files explicitly included.
2010-01-02doc: FreeBSD-specific notes + example code
2010-01-02Fix mq.notify = nil to unregister notifications
"mq.notify = false" also works now, doing what "mq.notify = nil" used to do (using SIGEV_NONE). I was confused by SIGEV_NONE usage vs using a NULL pointer for the notification passed mq_notify(3). SIGEV_NONE does not actually unregister, it registers a no-op notification which prevents other processes from taking us. This also fixes the test case to pass under both Linux and FreeBSD.
2010-01-02initial commit v0.1.0