* [sup-talk] sup web interface
@ 2010-04-30 5:43 Jason Petsod
2010-04-30 14:17 ` Nicholas Bergson-Shilcock
2010-04-30 23:13 ` Rich Lane
0 siblings, 2 replies; 9+ messages in thread
From: Jason Petsod @ 2010-04-30 5:43 UTC (permalink / raw)
To: sup-talk
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...
-Jason
[1] http://www.mail-archive.com/sup-talk@rubyforge.org/msg01536.html
[2] http://www.mail-archive.com/sup-talk@rubyforge.org/msg03192.html
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [sup-talk] sup web interface
2010-04-30 5:43 [sup-talk] sup web interface Jason Petsod
@ 2010-04-30 14:17 ` Nicholas Bergson-Shilcock
2010-04-30 14:57 ` Jon Dugan
2010-04-30 23:13 ` Rich Lane
1 sibling, 1 reply; 9+ messages in thread
From: Nicholas Bergson-Shilcock @ 2010-04-30 14:17 UTC (permalink / raw)
To: sup-talk
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'd love to see a web interface, particularly something that works well
from an iPhone or Android.
I don't have any strong preferences regarding the best web framework
for the job.
Thanks!
-Nick
>
> -Jason
>
> [1] http://www.mail-archive.com/sup-talk@rubyforge.org/msg01536.html
> [2] http://www.mail-archive.com/sup-talk@rubyforge.org/msg03192.html
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [sup-talk] sup web interface
2010-04-30 14:17 ` Nicholas Bergson-Shilcock
@ 2010-04-30 14:57 ` Jon Dugan
0 siblings, 0 replies; 9+ messages in thread
From: Jon Dugan @ 2010-04-30 14:57 UTC (permalink / raw)
To: sup-talk
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 <jdugan@es.net>
ESnet Network Engineering Group
Lawrence Berkeley National Laboratory
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [sup-talk] sup web interface
2010-04-30 5:43 [sup-talk] sup web interface Jason Petsod
2010-04-30 14:17 ` Nicholas Bergson-Shilcock
@ 2010-04-30 23:13 ` Rich Lane
2010-06-03 13:11 ` Andreas Happe
1 sibling, 1 reply; 9+ messages in thread
From: Rich Lane @ 2010-04-30 23:13 UTC (permalink / raw)
To: Jason Petsod; +Cc: sup-talk
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [sup-talk] sup web interface
2010-04-30 23:13 ` Rich Lane
@ 2010-06-03 13:11 ` Andreas Happe
2010-06-03 15:16 ` Rich Lane
0 siblings, 1 reply; 9+ messages in thread
From: Andreas Happe @ 2010-06-03 13:11 UTC (permalink / raw)
To: sup-talk
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
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [sup-talk] sup web interface
2010-06-03 13:11 ` Andreas Happe
@ 2010-06-03 15:16 ` Rich Lane
2010-06-04 12:01 ` Andreas Happe
0 siblings, 1 reply; 9+ messages in thread
From: Rich Lane @ 2010-06-03 15:16 UTC (permalink / raw)
To: Andreas Happe; +Cc: sup-talk
Excerpts from Andreas Happe's message of 2010-06-03 09:11:31 -0400:
> 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..
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.
> 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.
Link?
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [sup-talk] sup web interface
2010-06-03 15:16 ` Rich Lane
@ 2010-06-04 12:01 ` Andreas Happe
2010-06-04 15:59 ` Jason Petsod
0 siblings, 1 reply; 9+ messages in thread
From: Andreas Happe @ 2010-06-04 12:01 UTC (permalink / raw)
To: sup-talk
Rich Lane <rlane <at> club.cc.cmu.edu> writes:
> Excerpts from Andreas Happe's message of 2010-06-03 09:11:31 -0400:
> > 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.
>
> Link?
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.
cheers, Andreas
[0] http://www.github.org
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [sup-talk] sup web interface
2010-06-04 12:01 ` Andreas Happe
@ 2010-06-04 15:59 ` Jason Petsod
2010-06-05 3:55 ` Rich Lane
0 siblings, 1 reply; 9+ messages in thread
From: Jason Petsod @ 2010-06-04 15:59 UTC (permalink / raw)
To: sup-talk
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 :)
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.
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
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [sup-talk] sup web interface
2010-06-04 15:59 ` Jason Petsod
@ 2010-06-05 3:55 ` Rich Lane
0 siblings, 0 replies; 9+ messages in thread
From: Rich Lane @ 2010-06-05 3:55 UTC (permalink / raw)
To: Jason Petsod; +Cc: sup-talk
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
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2010-06-05 3:58 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-04-30 5:43 [sup-talk] sup web interface Jason Petsod
2010-04-30 14:17 ` Nicholas Bergson-Shilcock
2010-04-30 14:57 ` Jon Dugan
2010-04-30 23:13 ` Rich Lane
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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox