From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS6939 64.71.128.0/18 X-Spam-Status: No, score=-0.9 required=3.0 tests=AWL,BAYES_00,FREEMAIL_FROM, MSGID_FROM_MTA_HEADER shortcircuit=no autolearn=ham version=3.3.2 Path: news.gmane.org!not-for-mail From: Mark Peterson Newsgroups: gmane.comp.lang.ruby.kgio.general Subject: Re: JRuby Support Date: Sun, 1 Apr 2012 20:50:49 -0400 Message-ID: References: <20120302013750.GA15727@dcvr.yhbt.net> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Trace: dough.gmane.org 1333328357 14288 80.91.229.3 (2 Apr 2012 00:59:17 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 2 Apr 2012 00:59:17 +0000 (UTC) To: kgio@librelist.org Original-X-From: kgio@librelist.org Mon Apr 02 02:59:16 2012 Return-path: Envelope-to: gclrkg-kgio@m.gmane.org List-Archive: List-Help: List-Id: List-Post: List-Subscribe: List-Unsubscribe: Precedence: list Original-Sender: kgio@librelist.org Xref: news.gmane.org gmane.comp.lang.ruby.kgio.general:116 Archived-At: Received: from zedshaw.xen.prgmr.com ([64.71.167.205]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SEVc4-0007RR-1R for gclrkg-kgio@m.gmane.org; Mon, 02 Apr 2012 02:59:16 +0200 Received: from zedshaw.xen.prgmr.com (localhost [IPv6:::1]) by zedshaw.xen.prgmr.com (Postfix) with ESMTP id 7F0B921D5EB for ; Mon, 2 Apr 2012 01:05:44 +0000 (UTC) Content-Transfer-Encoding: 7bit X-Content-Filtered-By: PublicInbox::Filter 0.0.1 Thank you. I was barking up the wrong tree. On Thu, Mar 1, 2012 at 8:37 PM, Eric Wong wrote: > Mark Peterson wrote: > > I have unicorn and kgio working on Ruby on Rails app, but cannot install > > kgio on JRuby environment. > > kgio is only for Rubies that support C extensions. If you run JRuby > or unsupported systems, make kgio an optional dependency. > > kgio exists to expose (and hopefully fix) performance issues in MRI: > https://bugs.ruby-lang.org/issues/5138 > > Once MRI developers accept an API do non-blocking I/O without the > current overhead, kgio will be obsolete. >