I've noticed that Jun has this API in the bcms package, both a bcms::item::create_item and bcms::revision::add_revision.
It seems reasonable that we roll this functionality into the content repository itself.
Background: I'm writing the batch user synchronization code, and we typically get a big XML document with either all users, or changes since last update.
Now, in order for us to be able to track when there are problems, we've decided to store the entire document. And in order to not have to bother with CLOBs and such, we thought it might be simplest to just create a CR item for it, and simply deal with it through the CR API.
Except, of course, there is no such API that we can rely on in core.
What should we do?
1) Give up, and just put a CLOB column in our table (they're not *that* hard)
2) Roll Jun's BCMS API into acs-cotent-repository.
- Not sure what the status of the API is
- There's going to be some amount of work involved in renaming (I'm assuming we'd use cr:: namespace instead of bcms:: namespace, but keep everything else the same) and we won't have time to do this
- Is this consistent with what others are thinking?
3) Have other people been working on similar API? I seem to recall that Jeff wrote something like this for photo book.
4) Something else?
What are your thoughts?