Experimental IRC log happs-2007-11-19

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:19:35<nuncanada>cedricshock, that seems nice
00:20:18<nuncanada>happs has a separation out front for both post and get... So i guess it evens encorages you to separate both operations somewhat
00:20:38<cedricshock>Yeah. I think it'd make for a very nice site architecture.
00:21:56<cedricshock>I also think that only responding to POSTs with Location: headers would be nice from an end user point of view. The page that's a shown after a post should be something I can view again later, even if I've closed it or gone back.
00:26:06<cedricshock>Whether or not that page is guaranteed to be the same later on is a software design problem for the site. In some instances, like placing an order, it should be a constant receipt. Posting to a forum might have a composite view of the receipt and the current state, or even the current state highlighted to show all the posts more recent than the receipt. There might be some instances where the view would always be the current state, and n
00:26:06<cedricshock>ot at all historical (like a game).
02:07:14<cedricshock>I get the following error trying the new HAppS-Begin: runhaskell -ihaskell -i.haskell_cache/http_searchpath.org-default.map.cache haskell/Main.hs
02:07:14<cedricshock>.haskell_cache/http_searchpath.org-default.map.cache/HAppS/Data/Xml/Base.hs:3:34:
02:07:14<cedricshock> cannot parse LANGUAGE pragma
02:08:17<cedricshock>Any ideas what's going on?
02:45:12<nuncanada>Me too
02:45:31<nuncanada>It's been some time since i have been able to compile it
02:45:39<nuncanada>they are changing things all the time
03:10:22<kfish>cedricshock, nice idea for get/post handling
03:17:07<cedricshock>kfish: Thanks. I've found it very useful to separate server state changes from views, all the way out past the edge of the server. For example in a shopping system one might need to add something to the cart and return the cart ajax style, add something to the cart and return a shopping cart view, add something to the cart and get the same view back, or even add something to the cart and go to a completely different step, like checkout.
03:17:07<cedricshock>I'm not sure if using POST and GET consistently this way would improve the end user experience, but I plan on trying it.
03:29:48<kfish>cool
03:39:49<iseff>so, how do you get headers in 0.9.1?
03:45:27<iseff>?
09:24:21<iseff>anyone around?
11:40:38<Laney>Anybody alive? Has someone got a minimal example of state that will work with the current darcs code? Nothing I can find will compile :(
18:31:40<perspectivet>Saizan_: how did it go this weekend?
18:31:53<perspectivet>make any progress on hspread?
18:38:15<Saizan_>well, it's done, modulo api tweaking
18:40:45<perspectivet>cool
18:40:55<Saizan_>pushed
18:41:04<perspectivet>sorry I wasn't more help
18:41:18<Saizan_>no problem
18:41:45<Saizan_>if you've comments/suggestions on the api let me know :)
18:42:17<Saizan_>i should refine the export lists
18:42:38<Laney>ever thought of keeping a happs development blog?
18:51:24<Saizan_>perspectivet: ah, btw, still untested
18:51:37<perspectivet>completely untested?
18:52:28<Saizan_>err, yes..
18:52:45<perspectivet>ok
18:53:45<perspectivet>I'll find some time to play around testing it over the next couple of days

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