Perl 6 - the future is here, just unevenly distributed

IRC log for #webwork, 2013-10-04

| Channels | #webwork index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:06 mgage_ joined #webwork
00:59 rbeezer joined #webwork
03:21 rbeezer_ joined #webwork
12:22 mgage_ joined #webwork
13:15 mgage_ joined #webwork
14:12 goehle joined #webwork
16:22 goehle hey mgage
16:22 goehle I took a look through the webservice code
16:22 goehle what else should I look at?
17:08 rbeezer joined #webwork
19:10 goehle_ joined #webwork
19:10 goehle_ exit
19:30 mgage goehle: hi
19:30 goehle hey
19:31 mgage hi -- web service code is good -- peter and I are trying to hook his new ui up on my machine
19:31 mgage it involves getting dancer and apache to talk to each other
19:31 goehle ah
19:31 goehle ok
19:31 goehle I also did a dancer tutorial
19:31 mgage with luck we'll have it sorted out by tomorrow.
19:31 goehle and took a look at some of the new stuff
19:31 goehle I had a question about the naming conventions
19:31 mgage cool -- that's more than I did -- I'm working on a need to know basis :-)
19:31 mgage ok
19:32 goehle so dancer is being used for the web api
19:32 goehle but presumably it will also be used for the ui?
19:32 mgage it's actually being used for both
19:32 goehle right
19:32 goehle but we want to keep them kind of separate
19:32 goehle in my mind
19:32 mgage at least in one configuration   the feature/new-ui-stuff branch on Peter's github
19:32 goehle each page was its own dancer app
19:33 goehle and the api was a different app
19:33 goehle I was just confused because some of the api paths look like paths you would use for content
19:33 goehle things like
19:34 goehle /courses/:course_id/sets/:set_id
19:34 goehle look like the path you might use to find the set editor
19:34 mgage This is Peter here.  Right now, we're just using Dancer to do ajax requests.
19:34 mgage Dancer can send rendered html though
19:35 goehle so is the plan to eventually use dancer to make the ui as well?
19:35 mgage I would say loooonnnngg  term.  We should talk about this with the group.
19:35 goehle what serves the ui now
19:35 goehle ?
19:35 goehle still content generator?
19:35 mgage The .pm files in Content Generator
19:35 mgage Although those files are very bare bone.
19:36 goehle so why long term to switch over to something different
19:36 mgage The Problem View I tried to show at the online demo last week was a trial to see how to serve html using dancer.
19:36 goehle ah ok
19:37 mgage We should cover all of this with the group tomorrow.
19:37 goehle sure
19:37 goehle I'm just figuring things out
19:37 goehle is there a naming convention for the api
19:37 goehle for example, why not something like
19:38 goehle put_set
19:38 goehle or get_set
19:38 goehle instead of courses/:course_id/etc...
19:38 mgage the standard is to use a url for an object
19:38 mgage and then there is a http verb to say what to do with the object
19:38 goehle ah I see
19:39 goehle what about conflicting namespaces
19:39 mgage Example:  get all sets (global) from course xyz is  GET /courses/xyz/sets
19:39 goehle for example get /course/:courseid/sets/:setid
19:39 mgage that would get a single set
19:39 goehle could be reasonably used for the page which displays a set
19:39 goehle (like our ProblemSetDetail page right now)
19:40 mgage good question.  depends on the type of request.  It can serve an html page or an ajax and dancer can branch on the type.
19:40 goehle ah interesting, so ajax gets are different than html gets
19:40 goehle ok
19:41 goehle well thats something to think about
19:41 goehle I should get going though to catch my flight
19:41 mgage yep.
19:41 goehle thanks for answering my questions
19:41 mgage see you later tonight or tomorrow.  When do you land?
19:43 goehle latish.
19:43 goehle lateish (around 11pm)
22:07 aubreyja joined #webwork
22:07 aubreyja joined #webwork

| Channels | #webwork index | Today | | Search | Google Search | Plain-Text | summary