1 Aug 2011 16:46
Re: beanstalk-client ruby gem -- FD_CLOEXEC doesn't exist in windows
This has been working for me with various builds of Ruby 1.8.7:
if RUBY_PLATFORM.match(/i386-mswin32/) != nil ||
RUBY_PLATFORM.match(/i386-mingw32/) != nil ||
RUBY_PLATFORM.match(/cygwin/) != nil
-aeTkqpBoj2WDhNf7Hbop5Q@public.gmane.org(Fcntl::F_SETFL, Fcntl::O_NONBLOCK)
else-aeTkqpBoj2WDhNf7Hbop5Q@public.gmane.org(Fcntl::F_SETFD, Fcntl::FD_CLOEXEC)end
>> Anyways, commenting that one line renders a gem that seems to work for
>> me for development purposes in windows.
The FD_CLOEXEC flag is part of the POSIX API, which Windows doesn't support, but it does provide analogous functionality.
You can implement a patch with https://github.com/jarib/childprocess/ which appears to provide a consistent facade.
Cheers,
Jon
You received this message because you are subscribed to the Google Groups "beanstalk-talk" group.
To post to this group, send email to beanstalk-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to beanstalk-talk+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.
) so
wanted to replace the database based queue with beanstalkd. The issue
(obviously) is that each request that initiates the connection to the
server, reserves a job and then closes the connection - instantly
releasing the job.
So I have added a new command to the grammar of the protocol.
"preserve". This is only valid after a a job is reserved (in the same
way as "bury" works - however the preservation is only valid until the
existing reservation. It releases in the same way as a normal
reservation (i.e. when the expiry time is reached or if the server is
restarted and binary logging is enabled) but not if the connection is
dropped.
I have got this most of this working now so wanted to know how
interested people were.
cheers
Matt
RSS Feed