Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Rich Lane <rlane@club.cc.cmu.edu>
To: Jason Petsod <jason@petsod.org>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sup web interface
Date: Fri, 30 Apr 2010 19:13:36 -0400	[thread overview]
Message-ID: <1272644331-sup-1274@zyrg.net> (raw)
In-Reply-To: <1272606137-sup-842@acheron.quadco.net>

This is a great idea. I recommend using the sup-server protocol, either
natively or by running sup-cmd. That code has been in master for a while
now. I don't have a real opinion on web frameworks, but I'm biased
towards something lightweight.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  parent reply	other threads:[~2010-04-30 23:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-30  5:43 Jason Petsod
2010-04-30 14:17 ` Nicholas Bergson-Shilcock
2010-04-30 14:57   ` Jon Dugan
2010-04-30 23:13 ` Rich Lane [this message]
2010-06-03 13:11   ` Andreas Happe
2010-06-03 15:16     ` Rich Lane
2010-06-04 12:01       ` Andreas Happe
2010-06-04 15:59         ` Jason Petsod
2010-06-05  3:55           ` 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=1272644331-sup-1274@zyrg.net \
    --to=rlane@club.cc.cmu.edu \
    --cc=jason@petsod.org \
    --cc=sup-talk@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