ILL (Inter Library Loans).. with a fairly chunky amount of the code based on khalls Koha::Object classes, pianohackers Koha::Service object (which no-one out there has really seen yet) and the addition of AngularJS for the client side interface. Might get some people thinking though :)

put it this way magnuse.. I need somthing to show the boss by the end of the week.. we're on a sprint here with Colin working on British Library API integration and Alex working on the data storage and configuration side..

random interface question.. with Angular you can obviously affect dom with immediate effect without requiring a page reload.. so I have an option when adding a request.. to immediately add said request to the visible requests table, then highlight it and remove it if there's a failure between the client and the server.. or the other way around.. only adding to the user interface once the 'ok' signal has made it's way back from

ashimema: That seems reasonable enough. I think my only reason for not having allow_blessed enabled was to make sure that one didn't accidentally send something sensitive or gigantic back to the user, but if that causes more problems than it solves in practice go for it

ashimema: my understanding from the docs was that convert_blessed only converted objects that had an explicit TO_JSON method, whereas allow_blessed would attempt to convert everything, using a TO_JSON if it existed

we have a config object with the same general accessor pattern that utilises yaml as the storage medium.. and an api object that similarly has the same general accessor pattern that obviosly queries an api