rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: Joshua Peek <josh@joshpeek.com>
To: rack-devel@googlegroups.com
Subject: Re: Bloat?
Date: Thu, 13 Aug 2009 12:49:01 -0500	[thread overview]
Message-ID: <1c5622660908131049x72c4460ao460d858bbfe96a7c@mail.gmail.com> (raw)
In-Reply-To: <2a8d4a710908131004i2cef7cb7lc0be17ae7fe7619f@mail.gmail.com>


Here are a few candidates I'd like to see moved into rack-contrib.

Adapter::Camping
Auth::OpenID
ContentType
Recursive
Session::Memcache

On Thu, Aug 13, 2009 at 12:04 PM, Matt Todd<chiology@gmail.com> wrote:
> I was talking to a friend of mine yesterday and he mentioned that thought
> the Rack package itself seemed to be slightly bloated by things like Basic
> Auth et al. He mentioned two things I thought were interesting and I wanted
> to get your feedback on it:
> 1. Like Merb, Rack probably could benefit from using a core and more
> separation of functionality, and
> 2. Rack core should only include what's necessary for Rack::Lint to validate
> a basic application at minimum.
> Thoughts?
> Matt
> --
> Matt Todd
> Highgroove Studios
> www.highgroove.com
> cell: 404-314-2612
> blog: maraby.org
>
> Scout - Web Monitoring and Reporting Software
> www.scoutapp.com
>



-- 
Joshua Peek

  parent reply	other threads:[~2009-08-13 17:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13 17:04 Bloat? Matt Todd
2009-08-13 17:17 ` Bloat? Yehuda Katz
2009-08-13 17:45 ` Bloat? James Tucker
2009-08-13 17:49 ` Joshua Peek [this message]
2009-08-13 17:50   ` Bloat? James Tucker
2009-08-13 17:55     ` Bloat? Adrian Madrid
2009-08-13 18:54       ` Bloat? James Tucker
2009-08-13 20:20   ` Bloat? Christian Neukirchen
2009-08-13 17:49 ` Bloat? James Tucker
2009-08-13 19:01 ` Bloat? Ryan Tomayko
2009-08-13 19:19   ` Bloat? Matt Todd
2009-08-13 22:26     ` Bloat? James Tucker
2009-08-15  3:30 ` Bloat? Kyle Drake

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-list from there: mbox

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

  List information: https://groups.google.com/group/rack-devel

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

  git send-email \
    --in-reply-to=1c5622660908131049x72c4460ao460d858bbfe96a7c@mail.gmail.com \
    --to=rack-devel@googlegroups.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).