rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: Matt Todd <chiology@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: new middleware for rack-contrib: CAS
Date: Wed, 10 Jun 2009 13:05:16 -0400	[thread overview]
Message-ID: <2a8d4a710906101005x7e0e6aa7l5f3589029deb38bc@mail.gmail.com> (raw)
In-Reply-To: <135b7973-b7d5-4563-a102-4ba18cdc0bab@o36g2000vbi.googlegroups.com>

[-- Attachment #1: Type: text/plain, Size: 936 bytes --]

I'm certainly interested, just busy :) As long as it is quality (no doubt
that it is), it should be fine to assume that it'll be  in the next point
release. Not speaking authoritatively, mind.
Matt



On Wed, Jun 10, 2009 at 12:57 PM, Gaius <james.a.rosen@gmail.com> wrote:

>
> Still no interest in CAS? How do I go about getting it accepted to the
> master repository, and thus into the contrib section of the next Rack
> gem release?
>
> -Gaius
>
> On Jun 6, 3:32 pm, Gaius <james.a.ro...@gmail.com> wrote:
> > I built a CAS login middleware over the past week.
> >
> > The lighthouse ticket is here:
> http://rack.lighthouseapp.com/projects/22456/tickets/2-new-middleware...
> >
> > The code is here:
> http://github.com/gcnovus/rack-contrib/commit/322a598f3c4cc6cdfd3fbbd...




-- 
Matt Todd
Highgroove Studios
www.highgroove.com
cell: 404-314-2612
blog: maraby.org

Scout - Web Monitoring and Reporting Software
www.scoutapp.com

[-- Attachment #2: Type: text/html, Size: 1713 bytes --]

  reply	other threads:[~2009-06-10 17:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-06 19:32 new middleware for rack-contrib: CAS Gaius
2009-06-10 16:57 ` Gaius
2009-06-10 17:05   ` Matt Todd [this message]
2009-06-10 17:48   ` Ryan Tomayko
2009-06-11 11:48     ` Gaius

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=2a8d4a710906101005x7e0e6aa7l5f3589029deb38bc@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).