Subject: Re: [sup-talk] sup web interface

From: Andreas Happe <[email-masked]>
Date: Thu, 3 Jun 2010 13:11:31 +0000 (UTC)

Rich Lane <rlane <at> club.cc.cmu.edu> writes: 
> 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.

Wouldn't Rails[0] be the most obvious candidate? In addition since merb[1] was
merged (during the ongoing 3.0 development cycle) it might even count as
lightweight..

I won't start it (as I don't have nearly enough time on my hand), but might
contribute -- just put a rough (but working) prototype on github.

cheers, Andreas
[0] http://www.rubyonrails.org
[1] http://www.merbivore.com/

_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Rich Lane <[email-masked]>
Date: Fri, 04 Jun 2010 23:55:03 -0400

Excerpts from Jason Petsod's message of 2010-06-04 11:59:15 -0400:
> For threading, I had to add a new command 'thread' to sup-server, so you'll
> need to apply a patch [2] before it works. 

I've applied this to master. However, I think the final protocol support
for threading is going to be more complicated. Right now in the best
case this is going to result in a request for every thread displayed,
and in the worst case where thread requests are pipelined we could have
a lot of redundant message responses. The best I've come up with is
adding a "thread" option to query that mimics ThreadSet#load_n_threads.

> Also, it's not evident to me that the sup-server polls for new messages or
> has the ability to add new messages to the index, so checking for new
> messages or sending emails doesn't work yet. That functionality shouldn't
> hard to add though.

Yeah, I need to add a timer to periodically poll the sources. But it
should be possible to use the add request already to add sent messages
to the index.

I took a quick look at sup-web. I think it would be a good idea to spawn
an EM reactor thread when the webapp starts (if the server isnt already
using one) instead of starting one per sup protocol request. Similarly,
you'll probably want to keep a connection pool instead of opening a new
connection per sup protocol request.
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Jon Dugan <[email-masked]>
Date: Fri, 30 Apr 2010 09:57:53 -0500

Excerpts from Nicholas Bergson-Shilcock's message of Fri Apr 30 09:17:13 -0500 2010:
> I'd love to see a  web interface, particularly something that works well
> from an iPhone or Android.

+1 for a web interface, especially iPhone/iPad optimized.

Jon
-- 
Jon M. Dugan <[email-masked]>
ESnet Network Engineering Group
Lawrence Berkeley National Laboratory
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Rich Lane <[email-masked]>
Date: Fri, 30 Apr 2010 19:13:36 -0400

---

From: Rich Lane <[email-masked]>
Date: Thu, 03 Jun 2010 11:16:32 -0400

> merged (during the ongoing 3.0 development cycle) it might even count as

Sure. I really don't care what framework is used, I'll be happy just to
see a working web UI. At the time I was thinking that if the web UI code
were small enough it would be reasonable to keep it in the main Sup repo,
but now I'm not even sure that's desirable.

> contribute -- just put a rough (but working) prototype on github.

Link?

---

From: Nicholas Bergson-Shilcock <[email-masked]>
Date: Fri, 30 Apr 2010 10:17:13 -0400

Excerpts from Jason Petsod's message of Fri Apr 30 01:43:24 -0400 2010:
> Hi,
> 
> Is there still interest in a web interface for sup? There appear to be
> previous discussions on it [1][2], but it doesn't seem like anything
> conclusive was created.
> 
> If there is interest, is there a specific web framework (or no framework)
> the community would prefer? I might have some time this weekend to cobble
> something together...

I don't have any strong preferences regarding the best web framework
for the job.

Thanks!
  -Nick

> 
> -Jason
> 
> [1] http://www.mail-archive.com/[email-masked]/msg01536.html
> [2] http://www.mail-archive.com/[email-masked]/msg03192.html

---

From: Jason Petsod <[email-masked]>
Date: Fri, 30 Apr 2010 00:43:24 -0500

Hi,

-Jason

---

From: Jason Petsod <[email-masked]>
Date: Fri, 04 Jun 2010 10:59:15 -0500

On 04/06/2010 at 07:01:08 -0500, Andreas Happe wrote:
> To github[0]? My last sentence could have been clearer: I haven't put anything
> sup-related up on github, but if someone starts with a rough, but working,
> prototype I could help out.

I was able to start working on this a little bit [1] but it's currently
very rough around the edges. It uses the Sinatra framework, but most of the
actual logic is framework-agnostic so it could be pretty easily adapted
for another framework.

For threading, I had to add a new command 'thread' to sup-server, so you'll
need to apply a patch [2] before it works. The threading logic still needs
a little work; I roughly adapted sup's thread.rb, but added some bugs for
good measure :)

Cheers,
-Jason

[1] http://github.com/jasonpetsod/sup-web
[2] http://github.com/jasonpetsod/sup-web/raw/master/misc/expose_threading_on_sup-server.diff
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Andreas Happe <[email-masked]>
Date: Fri, 4 Jun 2010 12:01:08 +0000 (UTC)

cheers, Andreas

[0] http://www.github.org