tfpt review "/shelveset:IronRails2;REDMOND\tomat" Contains a simple change in DLR. Ruby changes: Improves IronRails - switches to IIS7 integrated mode, adds a log, implements static file handling. Updates Ruby HAPI. Fixes writing to text streams (\n should be replaced by \r\n). Ruby console host exposes the current Ruby engine via "iron_ruby" variable int the console scope. Tomas -------------- next part -------------- A non-text attachment was scrubbed... Name: IronRails2.diff Type: application/octet-stream Size: 15262 bytes Desc: IronRails2.diff URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20081017/bcc79299/attachment.obj>
Ruby and IronRails changes are good. The call to Handler.HandleFile could go outside of the Rails lock as there''s no Ruby code invoked. -----Original Message----- From: Tomas Matousek Sent: Friday, October 17, 2008 10:46 AM To: IronRuby External Code Reviewers; DLR Code Reviews Cc: ironruby-core at rubyforge.org Subject: Code Review: IronRails2 tfpt review "/shelveset:IronRails2;REDMOND\tomat" Contains a simple change in DLR. Ruby changes: Improves IronRails - switches to IIS7 integrated mode, adds a log, implements static file handling. Updates Ruby HAPI. Fixes writing to text streams (\n should be replaced by \r\n). Ruby console host exposes the current Ruby engine via "iron_ruby" variable int the console scope. Tomas
Now wait just a minute.... :) You can''t casually mention "IronRails changes look good" on the list without any indication of what IronRails is. That sounds far too exciting to pass up. Can someone explain what this might be to us non MSofties? -Eric On Fri, Oct 17, 2008 at 1:58 PM, Curt Hagenlocher <curth at microsoft.com>wrote:> Ruby and IronRails changes are good. > The call to Handler.HandleFile could go outside of the Rails lock as > there''s no Ruby code invoked. > > -----Original Message----- > From: Tomas Matousek > Sent: Friday, October 17, 2008 10:46 AM > To: IronRuby External Code Reviewers; DLR Code Reviews > Cc: ironruby-core at rubyforge.org > Subject: Code Review: IronRails2 > > tfpt review "/shelveset:IronRails2;REDMOND\tomat" > > Contains a simple change in DLR. > > Ruby changes: > Improves IronRails - switches to IIS7 integrated mode, adds a log, > implements static file handling. > Updates Ruby HAPI. > Fixes writing to text streams (\n should be replaced by \r\n). > Ruby console host exposes the current Ruby engine via "iron_ruby" variable > int the console scope. > > Tomas > > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20081017/80964db8/attachment-0001.html>
It''s a top secret experimental ASP.NET HttpHandler that dispatches to a Rails application :) Tomas From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Eric Nicholson Sent: Friday, October 17, 2008 11:48 AM To: ironruby-core at rubyforge.org Subject: Re: [Ironruby-core] Code Review: IronRails2 Now wait just a minute.... :) You can''t casually mention "IronRails changes look good" on the list without any indication of what IronRails is. That sounds far too exciting to pass up. Can someone explain what this might be to us non MSofties? -Eric On Fri, Oct 17, 2008 at 1:58 PM, Curt Hagenlocher <curth at microsoft.com<mailto:curth at microsoft.com>> wrote: Ruby and IronRails changes are good. The call to Handler.HandleFile could go outside of the Rails lock as there''s no Ruby code invoked. -----Original Message----- From: Tomas Matousek Sent: Friday, October 17, 2008 10:46 AM To: IronRuby External Code Reviewers; DLR Code Reviews Cc: ironruby-core at rubyforge.org<mailto:ironruby-core at rubyforge.org> Subject: Code Review: IronRails2 tfpt review "/shelveset:IronRails2;REDMOND\tomat" Contains a simple change in DLR. Ruby changes: Improves IronRails - switches to IIS7 integrated mode, adds a log, implements static file handling. Updates Ruby HAPI. Fixes writing to text streams (\n should be replaced by \r\n). Ruby console host exposes the current Ruby engine via "iron_ruby" variable int the console scope. Tomas _______________________________________________ Ironruby-core mailing list Ironruby-core at rubyforge.org<mailto:Ironruby-core at rubyforge.org> http://rubyforge.org/mailman/listinfo/ironruby-core -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20081017/f6be0c94/attachment.html>
It''s an IIS handler to calls Rails directly without going through Webrick or some other Ruby-based http server. It''s mostly experimental at this point. From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Eric Nicholson Sent: Friday, October 17, 2008 11:48 AM To: ironruby-core at rubyforge.org Subject: Re: [Ironruby-core] Code Review: IronRails2 Now wait just a minute.... :) You can''t casually mention "IronRails changes look good" on the list without any indication of what IronRails is. That sounds far too exciting to pass up. Can someone explain what this might be to us non MSofties? -Eric On Fri, Oct 17, 2008 at 1:58 PM, Curt Hagenlocher <curth at microsoft.com<mailto:curth at microsoft.com>> wrote: Ruby and IronRails changes are good. The call to Handler.HandleFile could go outside of the Rails lock as there''s no Ruby code invoked. -----Original Message----- From: Tomas Matousek Sent: Friday, October 17, 2008 10:46 AM To: IronRuby External Code Reviewers; DLR Code Reviews Cc: ironruby-core at rubyforge.org<mailto:ironruby-core at rubyforge.org> Subject: Code Review: IronRails2 tfpt review "/shelveset:IronRails2;REDMOND\tomat" Contains a simple change in DLR. Ruby changes: Improves IronRails - switches to IIS7 integrated mode, adds a log, implements static file handling. Updates Ruby HAPI. Fixes writing to text streams (\n should be replaced by \r\n). Ruby console host exposes the current Ruby engine via "iron_ruby" variable int the console scope. Tomas _______________________________________________ Ironruby-core mailing list Ironruby-core at rubyforge.org<mailto:Ironruby-core at rubyforge.org> http://rubyforge.org/mailman/listinfo/ironruby-core -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20081017/300290f2/attachment.html>
Can you tell that we all just got back from lunch? :) From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Tomas Matousek Sent: Friday, October 17, 2008 12:52 PM To: ironruby-core at rubyforge.org Subject: Re: [Ironruby-core] Code Review: IronRails2 It''s a top secret experimental ASP.NET HttpHandler that dispatches to a Rails application :) Tomas From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Eric Nicholson Sent: Friday, October 17, 2008 11:48 AM To: ironruby-core at rubyforge.org Subject: Re: [Ironruby-core] Code Review: IronRails2 Now wait just a minute.... :) You can''t casually mention "IronRails changes look good" on the list without any indication of what IronRails is. That sounds far too exciting to pass up. Can someone explain what this might be to us non MSofties? -Eric On Fri, Oct 17, 2008 at 1:58 PM, Curt Hagenlocher <curth at microsoft.com<mailto:curth at microsoft.com>> wrote: Ruby and IronRails changes are good. The call to Handler.HandleFile could go outside of the Rails lock as there''s no Ruby code invoked. -----Original Message----- From: Tomas Matousek Sent: Friday, October 17, 2008 10:46 AM To: IronRuby External Code Reviewers; DLR Code Reviews Cc: ironruby-core at rubyforge.org<mailto:ironruby-core at rubyforge.org> Subject: Code Review: IronRails2 tfpt review "/shelveset:IronRails2;REDMOND\tomat" Contains a simple change in DLR. Ruby changes: Improves IronRails - switches to IIS7 integrated mode, adds a log, implements static file handling. Updates Ruby HAPI. Fixes writing to text streams (\n should be replaced by \r\n). Ruby console host exposes the current Ruby engine via "iron_ruby" variable int the console scope. Tomas _______________________________________________ Ironruby-core mailing list Ironruby-core at rubyforge.org<mailto:Ironruby-core at rubyforge.org> http://rubyforge.org/mailman/listinfo/ironruby-core -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20081017/db332a1b/attachment-0001.html>
And Scott Guthrie said Microsoft had no interest in enabling Rails to run in IronRuby... :) On Fri, Oct 17, 2008 at 1:52 PM, Tomas Matousek < Tomas.Matousek at microsoft.com> wrote:> It''s a top secret experimental ASP.NET HttpHandler that dispatches to a > Rails application J > > > > Tomas > > > > *From:* ironruby-core-bounces at rubyforge.org [mailto: > ironruby-core-bounces at rubyforge.org] *On Behalf Of *Eric Nicholson > *Sent:* Friday, October 17, 2008 11:48 AM > *To:* ironruby-core at rubyforge.org > *Subject:* Re: [Ironruby-core] Code Review: IronRails2 > > > > Now wait just a minute.... > > :) > > You can''t casually mention "IronRails changes look good" on the list > without any indication of what IronRails is. That sounds far too exciting > to pass up. Can someone explain what this might be to us non MSofties? > > -Eric > > On Fri, Oct 17, 2008 at 1:58 PM, Curt Hagenlocher <curth at microsoft.com> > wrote: > > Ruby and IronRails changes are good. > The call to Handler.HandleFile could go outside of the Rails lock as > there''s no Ruby code invoked. > > > -----Original Message----- > From: Tomas Matousek > Sent: Friday, October 17, 2008 10:46 AM > To: IronRuby External Code Reviewers; DLR Code Reviews > Cc: ironruby-core at rubyforge.org > Subject: Code Review: IronRails2 > > tfpt review "/shelveset:IronRails2;REDMOND\tomat" > > Contains a simple change in DLR. > > Ruby changes: > Improves IronRails - switches to IIS7 integrated mode, adds a log, > implements static file handling. > Updates Ruby HAPI. > Fixes writing to text streams (\n should be replaced by \r\n). > Ruby console host exposes the current Ruby engine via "iron_ruby" variable > int the console scope. > > Tomas > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > > > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20081017/e6649946/attachment.html>
There''s quite a difference between a development environment like ASP.NET that''s fully supported by Microsoft and one that we make available on an as-is basis for the community to play with - and maybe take ownership of. Our goal has always been to create a fully conformant Ruby implementation, and by definition, that''s going to be able to run Rails. From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Mike Moore Sent: Friday, October 17, 2008 1:04 PM To: ironruby-core at rubyforge.org Subject: Re: [Ironruby-core] Code Review: IronRails2 And Scott Guthrie said Microsoft had no interest in enabling Rails to run in IronRuby... :) On Fri, Oct 17, 2008 at 1:52 PM, Tomas Matousek <Tomas.Matousek at microsoft.com<mailto:Tomas.Matousek at microsoft.com>> wrote: It''s a top secret experimental ASP.NET<http://ASP.NET> HttpHandler that dispatches to a Rails application :) Tomas From: ironruby-core-bounces at rubyforge.org<mailto:ironruby-core-bounces at rubyforge.org> [mailto:ironruby-core-bounces at rubyforge.org<mailto:ironruby-core-bounces at rubyforge.org>] On Behalf Of Eric Nicholson Sent: Friday, October 17, 2008 11:48 AM To: ironruby-core at rubyforge.org<mailto:ironruby-core at rubyforge.org> Subject: Re: [Ironruby-core] Code Review: IronRails2 Now wait just a minute.... :) You can''t casually mention "IronRails changes look good" on the list without any indication of what IronRails is. That sounds far too exciting to pass up. Can someone explain what this might be to us non MSofties? -Eric On Fri, Oct 17, 2008 at 1:58 PM, Curt Hagenlocher <curth at microsoft.com<mailto:curth at microsoft.com>> wrote: Ruby and IronRails changes are good. The call to Handler.HandleFile could go outside of the Rails lock as there''s no Ruby code invoked. -----Original Message----- From: Tomas Matousek Sent: Friday, October 17, 2008 10:46 AM To: IronRuby External Code Reviewers; DLR Code Reviews Cc: ironruby-core at rubyforge.org<mailto:ironruby-core at rubyforge.org> Subject: Code Review: IronRails2 tfpt review "/shelveset:IronRails2;REDMOND\tomat" Contains a simple change in DLR. Ruby changes: Improves IronRails - switches to IIS7 integrated mode, adds a log, implements static file handling. Updates Ruby HAPI. Fixes writing to text streams (\n should be replaced by \r\n). Ruby console host exposes the current Ruby engine via "iron_ruby" variable int the console scope. Tomas _______________________________________________ Ironruby-core mailing list Ironruby-core at rubyforge.org<mailto:Ironruby-core at rubyforge.org> http://rubyforge.org/mailman/listinfo/ironruby-core _______________________________________________ Ironruby-core mailing list Ironruby-core at rubyforge.org<mailto:Ironruby-core at rubyforge.org> http://rubyforge.org/mailman/listinfo/ironruby-core -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20081017/c3033ac9/attachment.html>
On Fri, Oct 17, 2008 at 2:09 PM, Curt Hagenlocher <curth at microsoft.com>wrote:> There''s quite a difference between a development environment like ASP.NETthat''s fully supported by Microsoft and one that we make available on an > as-is basis for the community to play with ? and maybe take ownership of. > Our goal has always been to create a fully conformant Ruby implementation, > and by definition, that''s going to be able to run Rails. >Sure, but the word before was that any ability to run Rails with IronRuby was not going to come from Microsoft and would have to be provided by the community. This looks to be coming directly from Microsoft. You could have left it alone and made us proxy from IIS to webrick/mongrel or use FastCGI, but this is evidence of the IronRuby team going above and beyond. You are to be commended. I would like to hear more chatter about this though. What are the results of your experiments with IronRails so far? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20081017/4b81611a/attachment.html>
The result so far is that it is able to dispatch a request to Rails and send output to client. The shelveset I''ve just submitted implements static file handling (so that static file requests are not dispatched to Rails). Tomas From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Mike Moore Sent: Friday, October 17, 2008 2:06 PM To: ironruby-core at rubyforge.org Subject: Re: [Ironruby-core] Code Review: IronRails2 On Fri, Oct 17, 2008 at 2:09 PM, Curt Hagenlocher <curth at microsoft.com<mailto:curth at microsoft.com>> wrote: There''s quite a difference between a development environment like ASP.NET<http://ASP.NET> that''s fully supported by Microsoft and one that we make available on an as-is basis for the community to play with - and maybe take ownership of. Our goal has always been to create a fully conformant Ruby implementation, and by definition, that''s going to be able to run Rails. Sure, but the word before was that any ability to run Rails with IronRuby was not going to come from Microsoft and would have to be provided by the community. This looks to be coming directly from Microsoft. You could have left it alone and made us proxy from IIS to webrick/mongrel or use FastCGI, but this is evidence of the IronRuby team going above and beyond. You are to be commended. I would like to hear more chatter about this though. What are the results of your experiments with IronRails so far? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20081017/b8777153/attachment-0001.html>
That''s great! Thanks for the update! -Eric On Fri, Oct 17, 2008 at 5:53 PM, Tomas Matousek < Tomas.Matousek at microsoft.com> wrote:> The result so far is that it is able to dispatch a request to Rails and > send output to client. The shelveset I''ve just submitted implements static > file handling (so that static file requests are not dispatched to Rails). > > > > Tomas > > > > *From:* ironruby-core-bounces at rubyforge.org [mailto: > ironruby-core-bounces at rubyforge.org] *On Behalf Of *Mike Moore > *Sent:* Friday, October 17, 2008 2:06 PM > *To:* ironruby-core at rubyforge.org > *Subject:* Re: [Ironruby-core] Code Review: IronRails2 > > > > On Fri, Oct 17, 2008 at 2:09 PM, Curt Hagenlocher <curth at microsoft.com> > wrote: > > There''s quite a difference between a development environment like ASP.NETthat''s fully supported by Microsoft and one that we make available on an > as-is basis for the community to play with ? and maybe take ownership of. > Our goal has always been to create a fully conformant Ruby implementation, > and by definition, that''s going to be able to run Rails. > > Sure, but the word before was that any ability to run Rails with IronRuby > was not going to come from Microsoft and would have to be provided by the > community. This looks to be coming directly from Microsoft. You could have > left it alone and made us proxy from IIS to webrick/mongrel or use FastCGI, > but this is evidence of the IronRuby team going above and beyond. You are to > be commended. > > > > I would like to hear more chatter about this though. What are the results > of your experiments with IronRails so far? > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20081018/57ee592c/attachment.html>