Time  Nick      Message
01:15 Arahael   So, I want to write a restful api.
01:16 Arahael   But I want to add search functionality to it - how can I do this while remaining restful?
01:16 Arahael   Or is such a search function orthogonal to rest?
01:47 talios    'lo
01:48 talios    I don't think so - you'd just have a search resource that returns links to other resources.
01:55 Arahael   As orthogonal to REST?
02:00 talios    no, as REST.    search is just a resource, that happens to return a representation of a query, with links to other resources.
02:01 Arahael   But that representation can change - and the client has to construct the uri?
02:02 talios    in our system for example, if we GET /api/search?s=talios we return a JSON document linking to matching documents.  representations change over time - like all resources.
02:02 talios    some other resource might link to your search service with a URI-Template, i.e. Link-Template: <http://localhost/api/search{?term}>; rel="search"
02:03 talios    then the client just resolves the template provided by the link-template, indirection and freedom for the server to change its location.  Sure, the rel and the template values are fixed...
02:04 Arahael   Where can I read about uri templates?
02:10 Arahael   (SPecifically, those link templates)
02:10 talios    http://tools.ietf.org/html/rfc6570 is the RFC for them
02:12 Arahael   Sweet, thanks for that.
02:13 Arahael   So my REST landing page would probably provide an index to the various resources, including the search resources, and allow the client to start navigating from there. Is that a good approach?
02:25 pdurbin   sounds discoverable, which is good
02:32 talios    sounds good
02:38 Arahael   Does providing an xml representation give any advantage to a REST API?
02:53 talios    over JSON?  XML is harder to consume nicely from Javascript, or so I hear.
02:53 talios    I guess it depends on your target users.  XML gives you DTDs/schemas you can exploit - if you care
04:07 Arahael   I guess it really gets down to that.
07:26 xyz_      hi
07:27 xyz_      i was trying to get the yahoo mail using yahoo yql rest api
07:27 xyz_      but i am getting error like  {"error":{"lang":"en-US","diagnostics":null,"description":"Authentication Error. The table ymail.messages requires a higher security level than is provided, you provided ANY but at least USER is expected"}}
07:27 xyz_      any idea what it means?
14:43 blongden  Hi all - I've made a load of updates to the vnd.error draft based on feedback thus far... would appreciate anyone with a little time to go through it and pick holes... https://github.com/blongden/vnd.error
14:43 blongden  It occured to me that I first created the draft over two years ago. Time flies.
15:24 pdurbin   "a simple way of expressing an error response in JSON" ... interesting
19:45 saml      hey, a resource has prev and next  (something like doubly linked list)
19:45 saml      if I PUT /resource/2,  it might affect up to three resources.  /resource/1, /resource/2, /resource/3    (if /resource/1 's next was /resource/3/)  does it make sense?
19:46 saml      PUT becomes non-idempotent
19:46 saml      PUT /resource/2     has side effects
20:00 fumanchu_ saml: so maintain the order as a separate resource
20:02 saml      example?
20:02 saml      /resource-orders
20:03 fumanchu_ sure. that can return an array or graph of links to resource/1, /2 etc..
20:04 fumanchu_ that also allows you a powerful separation between initialization (the PUT to resources/2) and activation (adding it to the array or graph)
20:05 fumanchu_ and allows for multiple orders: per-user, or different indices for different needs
20:19 saml      there are over 500k resources  like /resource/1