Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Mark Alexander <marka@pobox.com>
To: Rich Lane <rlane@club.cc.cmu.edu>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] new branch: maildir
Date: Thu, 25 Mar 2010 07:24:59 -0400	[thread overview]
Message-ID: <1269516077-sup-4573@r61> (raw)
In-Reply-To: <1269499582-sup-2593@zyrg.net>

Excerpts from Rich Lane's message of Thu Mar 25 03:12:57 -0400 2010:
> This branch makes some drastic changes to how mbox and maildir sources
> work.

Thanks for attacking this problem!

I just took a quick look at the diffs, and I have some concern
about this line in maildir.rb:

  Dir[File.join(subdir, '*')].map do |fn|

I'm worried about the memory usage with some of my maildirs that have
tens of thousands of files.  Would it be more memory-efficient to
use Dir.open and Dir.each?  You'd have to filter out "." and "..",
of course.
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


  reply	other threads:[~2010-03-25 12:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25  7:12 Rich Lane
2010-03-25 11:24 ` Mark Alexander [this message]
2010-03-25 13:30   ` Ben Walton
2010-03-25 16:11   ` Rich Lane

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

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

  git send-email \
    --in-reply-to=1269516077-sup-4573@r61 \
    --to=marka@pobox.com \
    --cc=rlane@club.cc.cmu.edu \
    --cc=sup-devel@rubyforge.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox