greptilian logo

IRC log for #rest, 2017-01-10

#rest on freenode has been logged here from May 2014 until end of July 2018 but logging has been suspended because the channel has been riddled with spam since August 2018 with no end in site. See the following blog posts about the problem:

Until the spam problem has been dealt with and logging can resume, please visit our wiki at https://trygvis.io/rest-wiki/

Thanks.

| Channels | #rest index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

All times shown according to UTC.

Time S Nick Message
02:00 fuzzyhorns joined #rest
02:12 metrixx joined #rest
02:40 fuzzyhorns joined #rest
06:30 sp1rs joined #rest
06:57 sp1rs joined #rest
07:03 sp1rs joined #rest
08:20 sp1rs joined #rest
08:29 wsieroci joined #rest
08:58 metrixx joined #rest
09:23 interop_madness joined #rest
09:27 metrixx joined #rest
09:35 Davey joined #rest
09:35 Davey joined #rest
09:37 blongden_ joined #rest
09:37 rxo joined #rest
09:37 mooncup joined #rest
09:37 mooncup joined #rest
09:39 `0660 joined #rest
09:49 sp1rs joined #rest
10:05 sp1rs joined #rest
10:09 sp1rs joined #rest
11:31 sp1rs joined #rest
11:36 wsieroci joined #rest
11:50 sp1rs joined #rest
12:54 sp1rs joined #rest
12:59 shodan` joined #rest
13:09 interop_madness joined #rest
14:53 saml_ joined #rest
14:53 saml_ for publish/unpublish what do you use? POST?
14:53 saml_ or,  PATCH /pages/1    with {"status": "published"}  ?
14:54 saml_ vs.   POST /pages/1/publish
14:54 asdf yeah, the latter is pretty rpc, isn't it?
14:55 asdf the "update status" one is indeed the usual way
14:56 saml_ there's requirement that it can be unpublished only once after being published
14:57 saml_ would you encode that state restriction in API? or let clients implement ?
14:57 saml_ like, you can publish a page, unpublish it, and then publish it again. then the page is forever published.
14:57 saml_ once it's re-published,  you cannot unpublish any more
14:58 saml_ and, i'd like version pages as they are published
14:58 asdf yeah, i'd add some value to it so that the client was able to display a "this was published before, are you sure you want to publish again" warning
14:58 saml_ so, I wanted special POST /pages/1/publish  endpoint instead of generic PATCH /pages/1/
14:59 asdf another way is to have /pages and /published, and create a resource in published linking to one from pages
14:59 asdf (and delete to unpublish)
14:59 asdf if there's a lot of metadata related to the publishing then that might be nicer
14:59 saml_ POST /pages/1/publish    creates resource /published/1 ?
15:00 asdf no, just POST /published/1 {"page": "/pages/1"}
15:00 asdf well, PUT (or POST /published)
15:00 asdf /publications, i guess :p
15:01 saml_ hrm.. /publications/1  would be links  or actual copy of /pages/1?
15:01 asdf i'd make it links, but i suppose depends on if you want to make pages mutable (and what do you want that to do to publications)
15:02 saml_ i guess clients would like it if /publications/1  and /pages/1 's representations  are the same.  except /publications/1  would contain more metadata
15:02 asdf and maybe /pages/1 would have a publishedCount or something (or a wasPublished flag) for your other requirement
15:03 saml_ i'll have to think about it and play around. thank you
15:04 saml_ never would have come up with /publiscations/1
15:27 sp1rs joined #rest
15:55 sp1rs joined #rest
16:13 sp1rs joined #rest
16:54 fuzzyhorns1 joined #rest
16:56 fuzzyhorns1 joined #rest
16:57 fuzzyhorns1 joined #rest
16:58 sp1rs joined #rest
16:59 fuzzyhorns1 joined #rest
16:59 fuzzyhorns1 joined #rest
17:01 fuzzyhorns1 joined #rest
17:01 fuzzyhorns1 joined #rest
17:13 sp1rs joined #rest
17:19 sp1rs joined #rest
17:39 sp1rs joined #rest
18:18 wsieroci joined #rest
18:28 sp1rs joined #rest
18:54 wsieroci joined #rest
19:44 sp1rs joined #rest
19:47 wsieroci joined #rest
20:13 wsieroci joined #rest
21:00 wsieroci joined #rest
21:40 sp1rs joined #rest
22:21 fuzzyhorns joined #rest
22:56 sp1rs joined #rest
23:04 fuzzyhorns joined #rest

| Channels | #rest index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

#rest on freenode has been logged here from May 2014 until end of July 2018 but logging has been suspended because the channel has been riddled with spam since August 2018 with no end in site. See the following blog posts about the problem:

Until the spam problem has been dealt with and logging can resume, please visit our wiki at https://trygvis.io/rest-wiki/

Thanks.