 |
 |
Ross Singer wrote: > Unlike Twitter, however, we're starting from nothing. There's nothing > currently invested in ILS-DI clients that would break by committing > solely to OAuth (or anything, for that matter). Are you sure there's nothing currently invested? I thought the Koha community was already implementing ILS-DI so I assume there's some client using it, as people don't tend to fund useless developments. I don't remember if any of the co-op's client libraries are using it yet, though. [ILS-DI] > It's no longer under the auspices of the DLF and the priority of > functionality has changed. [...] OK, if it's no longer under the auspices of the DLF are you still in contact with BibLibre? > Indeed, and I hope the reply was likewise helpful. It was. More answers than questions, which is always good! That said, I'm still not seeing the benefits of OAuth for ILS-DI compared to existing HTTP authentication and authorization methods, really. Regards, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. Past Koha Release Manager (2.0), LMS programmer, statistician, webmaster. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha