Rainbows! Rack HTTP server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>
To: Pratik Naik <pratiknaik-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Rainbows! list
	<rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org>,
	"Lin Jen-Shin \(godfat\)"
	<godfat-hOE/xeEBYYIdnm+yROfE0A@public.gmane.org>
Subject: Cramp support for Ruby 2.0?
Date: Mon, 23 Sep 2013 22:44:35 +0000	[thread overview]
Message-ID: <20130923224435.GA9842@dcvr.yhbt.net> (raw)
In-Reply-To: <CAA2_N1sDC2bJd8kQC+V2_M=UAL2xrUYEjWPS5hWBwmXiN6LM6w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

(Pulling Pratik into the discussion)

Hi Pratik, just wondering if you're still interested in Cramp.

It doesn't seem to work on Ruby 2.0 (see messages below), but if you're
no longer interested, that's totally fine; we'll just point users
elsewhere.  I don't think Cramp ever really took off and EM seems to
be losing traction, too.

"Lin Jen-Shin (godfat)" <godfat-hOE/xeEBYYIdnm+yROfE0A@public.gmane.org> wrote:
> On Sat, Sep 14, 2013 at 2:19 AM, Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org> wrote:
> > EM 1.0.3 doesn't seem to work with Cramp.  Can you try? I probably won't
> > have time to look further for at least a week.
> >
> > Thanks.
> 
> Umm... looks like Cramp doesn't even run smooth on Ruby 2.0 (or even 1.9?)
> I just tried EM 1.0.3 with Cramp 0.15.1, there's an encoding issue in:
> 
>     t/tmp/isolate/ruby-2.0.0/cramp/gems/cramp-0.15.1/lib/cramp/callbacks.rb:82
> 
> Which has an improper regexp:
> 
>     /\000([^\377]*)\377/
> 
> After adding magic binary encoding on top of the file:
> 
>     # encoding: binary
> 
> Then all tests in EventMachine.t0500-cramp-streaming.sh and
> EventMachine.t0501-cramp-rainsocket.sh passed.
> 
> What should we do here? Are people even using Cramp..?
> It seems it's not updated for two years already.
> 
> Please take your time, thanks!
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying


      parent reply	other threads:[~2013-09-23 22:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-12 16:48 [PATCH] Update eventmachine to 1.0.3 which compiles under Ruby 2.0 Lin Jen-Shin
     [not found] ` <1379004491-71337-1-git-send-email-godfat-hOE/xeEBYYIdnm+yROfE0A@public.gmane.org>
2013-09-13 18:19   ` Eric Wong
     [not found]     ` <20130913181933.GA11118-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2013-09-13 19:13       ` Lin Jen-Shin (godfat)
     [not found]         ` <CAA2_N1sDC2bJd8kQC+V2_M=UAL2xrUYEjWPS5hWBwmXiN6LM6w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-23 22:44           ` Eric Wong [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/rainbows/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130923224435.GA9842@dcvr.yhbt.net \
    --to=normalperson-rmlxzr9ms24@public.gmane.org \
    --cc=godfat-hOE/xeEBYYIdnm+yROfE0A@public.gmane.org \
    --cc=pratiknaik-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org \
    --subject='Re: Cramp support for Ruby 2.0?' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

	../../rainbows.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).