Peta Ward
2012-Dec-14 12:01 UTC
Re: Digest for rubyonrails-core@googlegroups.com - 4 Messages in 3 Topics
This is a delivery failure notification message indicating that an email you sent could not be delivered. The problem appears to be : -- Recipient email server rejected the message This condition occurred after 1 attempt(s) to deliver over a period of 0 hour(s). If you sent the email to multiple recipients, you will receive one of these messages for each one which failed delivery, otherwise they have been sent. On 14 Dec 2012, at 11:59, rubyonrails-core@googlegroups.com wrote:> Today''s Topic Summary > Group: http://groups.google.com/group/rubyonrails-core/topics > • Proposal: ActionController class methods, all procs get evaluated [2 Updates] > • Should render collection: @items have a cache option so that read_multi can be utilized? [1 Update] > • Digest for rubyonrails-core@googlegroups.com - 1 Message in 1 Topic [1 Update] > Proposal: ActionController class methods, all procs get evaluated > • Scott Carleton <carleton.scott@gmail.com> Dec 13 09:35AM -0800 > • > • Specifically looking at action_cache in Rails.3.2 stable right now. > • > • It currently will evaluate procs given to the layout or cache_path as can beseen here<https://github.com/rails/rails/blob/3-2-stable/actionpack/lib/action_controller/caching/actions.rb#L135>. > • > • > • I''m working on a library where I''d like to tag my caches so that I can > • expire sets of keys easily. It would appear that something such as > • > • caches_action :show, tag: Proc.new { "post_#{params[:id]}" } > • > • would evaluate to the tag to post_1, post_2 etc but it doesn''t. It > • wouldn''t take much to modify the filter method linked above to evaluate > • all procs passed in as options. I''m going to make a pull request unless > • there are any objections. > • > • "Rafael Mendonça França" <rafaelmfranca@gmail.com> Dec 13 06:28PM -0300 > • > • Action cache was extracted from Rails and it is not part of the framework > • anymore. > • > • Rafael Mendonça França > • http://twitter.com/rafaelfranca > • https://github.com/rafaelfranca > • > • > • > • > Should render collection: @items have a cache option so that read_multi can be utilized? > • nate <nate@inventric.com> Dec 13 08:21AM -0800 > • > • I released a gem yesterday > • > • https://github.com/n8/multi_fetch_fragments > • > • that adds this syntax on rendering a collection of partials: > • > • <%= render partial: ''item'', collection: @items, cache: true %> > • > • > • And then the gem uses Rails read_multi to fetch any cached fragments of > • this partial. It can be a pretty big speed boost instead of fetching from > • Memcached sequentially. One guy saw a 93% improvement on an action of his > • that was simply rendering out 25 items. > • > • Some folks have been asking me to post to this list to see if this is > • something that I should write a pull request for against Rails to become a > • standard feature? > • > • -Nate > • > Digest for rubyonrails-core@googlegroups.com - 1 Message in 1 Topic > • Peta Ward <peterwardhowlett@gmail.com> Dec 13 12:45PM > • > • This is a delivery failure notification message indicating that > • an email you sent could not be delivered. The problem appears to be : > • -- Recipient email server rejected the message > • > • This condition occurred after 1 attempt(s) to deliver over > • a period of 0 hour(s). > • > • If you sent the email to multiple recipients, you will receive one > • of these messages for each one which failed delivery, otherwise > • they have been sent. > • > • > You received this message because you are subscribed to the Google Group rubyonrails-core. > You can post via email. > To unsubscribe from this group, send an empty message. > For more options, visit this group. > > -- > You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. > To post to this group, send email to rubyonrails-core@googlegroups.com. > To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Chad Woolley
2012-Dec-14 14:42 UTC
Re: Digest for rubyonrails-core@googlegroups.com - 4 Messages in 3 Topics
Removed from group... -- Chad On Fri, Dec 14, 2012 at 5:01 AM, Peta Ward <peterwardhowlett@gmail.com> wrote:> This is a delivery failure notification message indicating that > an email you sent could not be delivered. The problem appears to be : > -- Recipient email server rejected the message > > This condition occurred after 1 attempt(s) to deliver over > a period of 0 hour(s). > > If you sent the email to multiple recipients, you will receive one > of these messages for each one which failed delivery, otherwise > they have been sent. > > On 14 Dec 2012, at 11:59, rubyonrails-core@googlegroups.com wrote: > >> Today''s Topic Summary >> Group: http://groups.google.com/group/rubyonrails-core/topics >> • Proposal: ActionController class methods, all procs get evaluated [2 Updates] >> • Should render collection: @items have a cache option so that read_multi can be utilized? [1 Update] >> • Digest for rubyonrails-core@googlegroups.com - 1 Message in 1 Topic [1 Update] >> Proposal: ActionController class methods, all procs get evaluated >> • Scott Carleton <carleton.scott@gmail.com> Dec 13 09:35AM -0800 >> • >> • Specifically looking at action_cache in Rails.3.2 stable right now. >> • >> • It currently will evaluate procs given to the layout or cache_path as can beseen here<https://github.com/rails/rails/blob/3-2-stable/actionpack/lib/action_controller/caching/actions.rb#L135>. >> • >> • >> • I''m working on a library where I''d like to tag my caches so that I can >> • expire sets of keys easily. It would appear that something such as >> • >> • caches_action :show, tag: Proc.new { "post_#{params[:id]}" } >> • >> • would evaluate to the tag to post_1, post_2 etc but it doesn''t. It >> • wouldn''t take much to modify the filter method linked above to evaluate >> • all procs passed in as options. I''m going to make a pull request unless >> • there are any objections. >> • >> • "Rafael Mendonça França" <rafaelmfranca@gmail.com> Dec 13 06:28PM -0300 >> • >> • Action cache was extracted from Rails and it is not part of the framework >> • anymore. >> • >> • Rafael Mendonça França >> • http://twitter.com/rafaelfranca >> • https://github.com/rafaelfranca >> • >> • >> • >> • >> Should render collection: @items have a cache option so that read_multi can be utilized? >> • nate <nate@inventric.com> Dec 13 08:21AM -0800 >> • >> • I released a gem yesterday >> • >> • https://github.com/n8/multi_fetch_fragments >> • >> • that adds this syntax on rendering a collection of partials: >> • >> • <%= render partial: ''item'', collection: @items, cache: true %> >> • >> • >> • And then the gem uses Rails read_multi to fetch any cached fragments of >> • this partial. It can be a pretty big speed boost instead of fetching from >> • Memcached sequentially. One guy saw a 93% improvement on an action of his >> • that was simply rendering out 25 items. >> • >> • Some folks have been asking me to post to this list to see if this is >> • something that I should write a pull request for against Rails to become a >> • standard feature? >> • >> • -Nate >> • >> Digest for rubyonrails-core@googlegroups.com - 1 Message in 1 Topic >> • Peta Ward <peterwardhowlett@gmail.com> Dec 13 12:45PM >> • >> • This is a delivery failure notification message indicating that >> • an email you sent could not be delivered. The problem appears to be : >> • -- Recipient email server rejected the message >> • >> • This condition occurred after 1 attempt(s) to deliver over >> • a period of 0 hour(s). >> • >> • If you sent the email to multiple recipients, you will receive one >> • of these messages for each one which failed delivery, otherwise >> • they have been sent. >> • >> • >> You received this message because you are subscribed to the Google Group rubyonrails-core. > You can post via email. > To unsubscribe from this group, send an empty message. > For more options, visit this group. >> >> -- >> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. >> To post to this group, send email to rubyonrails-core@googlegroups.com. >> To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. > > -- > You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. > To post to this group, send email to rubyonrails-core@googlegroups.com. > To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. >-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.