I've been pouring over BreezeJS documentation and stackoverflow posts looking for definitive information on using BreezeJS to interact with a REST tier (not .NET) that supports CRUD operations. I've read a number of posts that clearly communicates the philosophy behind the default behavior of saveChanges() which sends a collection of updated entities to the server. While creating server-side code to handle this may be possible it is likely that won't be our preferred path and yes, I do understand that there are transactional and state issues that decision would inflict on the client code.
In my searches on stackoverflow I've found a number of questions that are similar to mine, but those questions are all relatively old (at least for JavaScript libraries) - (ex. Save changes to RESTful URLS with Breeze JS).
Some of those posts, including the one above, seem to indicate that work is/has been done to address the desire to do CRUD operations via normal REST operations.
Finally my questions: What is the current state of BreezeJS with regard to supporting RESTful CRUD operations? If I choose to manage the entity updates via a named save operation what kinds of hoops will I need to jump through to get Breeze to send those CRUD operations to my REST tier? What else am I missing in my summary above that will make CRUD operations from BreezeJS to a REST tier challenging?
Note: our JavaScript framework is Angular.
