deferrable bodies in Rainbows!

deferrable bodies in Rainbows!

[Eric Wong]

Moving to rainbows list

James Tucker <jftucker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Eric - I had a report from one of the async_sinatra users who tried
> out rainbows with EM, and found that the API didn't actually line up
> with what Thin was doing. I really want to devote some more time with
> this but I've been very busy. Sadly due to this I don't want to say
> stop, but, well, I want to say please check existing apps against it.
> I guess could you check async_*.ru from
> github.com/macournoyer/thin/master/tree/examples/async_*.ru, as from
> what was reported, they're not working with the rainbows
> implementation of the deferrablebody hacks.

Hi James, thhanks for the heads up.

Rainbows! doesn't handle deferrable bodies yet (I didn't look closely enough
the first time around), so it can't do everything Thin does with EM, yet.
It's already in the TODO, I'll make a mental note to work on it sooner.

-- 
Eric Wong
_______________________________________________
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

Re: deferrable bodies in Rainbows!

[James Tucker]

On 26 Dec 2009, at 23:27, Eric Wong wrote:

> Moving to rainbows list
> 
> James Tucker <jftucker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> Eric - I had a report from one of the async_sinatra users who tried
>> out rainbows with EM, and found that the API didn't actually line up
>> with what Thin was doing. I really want to devote some more time with
>> this but I've been very busy. Sadly due to this I don't want to say
>> stop, but, well, I want to say please check existing apps against it.
>> I guess could you check async_*.ru from
>> github.com/macournoyer/thin/master/tree/examples/async_*.ru, as from
>> what was reported, they're not working with the rainbows
>> implementation of the deferrablebody hacks.
> 
> Hi James, thhanks for the heads up.
> 
> Rainbows! doesn't handle deferrable bodies yet (I didn't look closely enough
> the first time around), so it can't do everything Thin does with EM, yet.
> It's already in the TODO, I'll make a mental note to work on it sooner.

Making this stuff work correctly in sync and async is one of the things that kills a rack.io style api, particularly for an abstracted IO layer like eventmachine (where you can't extract and hand out the raw IO without causing signficant complication + problems (we're never gunna support read(3) and EM buffered reads in concurrently under EM for obvious reasons)). This means such APIs can be problematic to implement properly, forcing people to buffer and pack in StringIO and whatnot. There are some more hacks one can do ofc, but I'd rather come up with an API that's good for all, whilst still being performant (this is possible, I am certain).

Sorry for yet another rushed reply (starting to feel real bad about that over here) :(

P.S. This S/MIME rejection is really starting to grate me, I'm wishing Mail.app had the ability to forcibly stop doing that for specific addresses, but their S/MIME support is as embedded as most other clients (for mostly better, and occasionally worse).
_______________________________________________
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

Re: deferrable bodies in Rainbows!

[Eric Wong]

James Tucker <jftucker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
(snip stuff I mostly agree with, pondering some still...)
> Sorry for yet another rushed reply (starting to feel real bad about
> that over here) :(

No worries, at least the message got through.

> P.S. This S/MIME rejection is really starting to grate me, I'm wishing
> Mail.app had the ability to forcibly stop doing that for specific
> addresses, but their S/MIME support is as embedded as most other
> clients (for mostly better, and occasionally worse).

I'll consider allowing signatures if it makes your life easier...

However I strongly believe the content of messages trumps the identity
of the sender, and signatures in public correspondence shouldn't matter.

-- 
Eric Wong
_______________________________________________
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

Re: deferrable bodies in Rainbows!

[James Tucker]

On 27 Dec 2009, at 02:16, Eric Wong wrote:

> James Tucker <jftucker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> (snip stuff I mostly agree with, pondering some still...)
>> Sorry for yet another rushed reply (starting to feel real bad about
>> that over here) :(
> 
> No worries, at least the message got through.
> 
>> P.S. This S/MIME rejection is really starting to grate me, I'm wishing
>> Mail.app had the ability to forcibly stop doing that for specific
>> addresses, but their S/MIME support is as embedded as most other
>> clients (for mostly better, and occasionally worse).
> 
> I'll consider allowing signatures if it makes your life easier...

No don't worry, I just need to get used to it :-S

> 
> However I strongly believe the content of messages trumps the identity
> of the sender, and signatures in public correspondence shouldn't matter.

I'd agree if I hadn't had a distasteful person spoof me in the past in an attempt to defame my character. The person in question was reprimanded, but, in that case it was easy to track him down - not that I expect that to happen in this community.

Don't worry about changing anything, I'll stop whining (sorry) :)

> -- 
> Eric Wong
> _______________________________________________
> 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

_______________________________________________
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

Re: deferrable bodies in Rainbows!

[Eric Wong]

Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org> wrote:
> Moving to rainbows list
> 
> James Tucker <jftucker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > Eric - I had a report from one of the async_sinatra users who tried
> > out rainbows with EM, and found that the API didn't actually line up
> > with what Thin was doing. I really want to devote some more time with
> > this but I've been very busy. Sadly due to this I don't want to say
> > stop, but, well, I want to say please check existing apps against it.
> > I guess could you check async_*.ru from
> > github.com/macournoyer/thin/master/tree/examples/async_*.ru, as from
> > what was reported, they're not working with the rainbows
> > implementation of the deferrablebody hacks.
> 
> Hi James, thhanks for the heads up.
> 
> Rainbows! doesn't handle deferrable bodies yet (I didn't look closely enough
> the first time around), so it can't do everything Thin does with EM, yet.
> It's already in the TODO, I'll make a mental note to work on it sooner.

Rainbows! 0.90.1 should support deferrable bodies needed for async apps
on EM.

I stole the async_app.ru and async_tailer.ru examples from Thin and made
them a part of the integration tests (in t/t04??-*.sh).


The app.deferred?(env) isn't supported, yet.  It's in the TODO and I
don't think many people use it... (correct me if I'm wrong).

-- 
Eric Wong
_______________________________________________
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