Experimental IRC log happs-2008-03-06

Available formats: content-negotiated html turtle (see SIOC for the vocabulary)

Back to channel and daily index: content-negotiated html turtle

These logs are provided as an experiment in indexing discussions using IRCHub.py, Irc2RDF.hs, and SIOC.

00:42:31<dbpatterson>next iteration of the mightybyte clone HAppS tutorial up at http://dbpatterson.com/blog/4711479980
00:42:48<dbpatterson>again, comments, questions, critiques welcome
00:54:29<Saizan>dbpatterson: nice article, i like that requireLogin :)
00:56:06<Saizan>we should put together a session module out of these posts and keep it in HappS-Server or -Agents
01:06:54<dbpatterson>Saizan: that's what I was thinking
01:07:09<dbpatterson>the person who hosted mightybyte's app created a google code group for it
01:07:22<dbpatterson>not sure if that is a little overkill, but at least that is one more person who is interested
01:07:42<dbpatterson>at http://code.google.com/p/happs-tutorial/source/checkout
01:08:32<dbpatterson>something I was wondering... seeOther takes a url and also a Response, what is the Response for?
01:08:54<dbpatterson>can you capture it in any way (ideally from the url you directed to)?
01:09:41<Saizan>seeOther sends a response with a Location header iirc, so the redirection goes via the browser
01:10:10<Saizan>which normally doesn't show the body of the response
01:10:13<dbpatterson>Saizan: so no faking a continuation passing webserver :)
01:10:37<Saizan>no :)
01:12:02<dbpatterson>something I was thinking about was how to store session based short messages (something along the lines of ruby on rails 'flash')
01:12:31<dbpatterson>is there a better way to implement that kind of behavior?
01:13:19<Saizan>never used rails
01:13:34<Saizan>can you elaborate?
01:13:47<dbpatterson>well, to be honest, I've never really used it either
01:13:51<dbpatterson>but from what I was reading
01:13:57<dbpatterson>you can store a simple message
01:14:10<dbpatterson>so that you check for it and print it if it exists
01:14:17<dbpatterson>so if you redirect to the login page
01:14:28<dbpatterson>the login page can check if that message exists, and if it does, print it
01:14:43<dbpatterson>but more generally
01:14:52<dbpatterson>the idea is a session based short text storage (I think)
01:15:21<dbpatterson>and on the top of any page you would print it in its own special box (well, this is what I would do)
01:16:04<Saizan>HAppS still doesn't have a specific infrastructure to build pages
01:16:25<Saizan>so it would really depend on how you do them
01:17:09<dbpatterson>hmm.. maybe the easiest way to do this would be to just stick a cookie on the web browser and look for _it_
01:17:15<Saizan>as for the storing part, a little problem is that sessions can store only one type, so they're not very flexible
01:18:26<Saizan>that's not a bad idea, but including code that comes from the user in your pages expose yourself to attacks
01:18:37<dbpatterson>that's true
01:19:11<dbpatterson>definitely ideal
01:19:14<dbpatterson>not ideal*
01:19:35<dbpatterson>maybe I'll try to put something together and come back when I have more concrete ideas :) or something to show for it
15:27:48<fxr>anybody using happs-plugins?

Back to channel and daily index: content-negotiated html turtle