I'm currently using the core service
SaveApplicationData method - sequentially adding new application data to both a specific subject (TCM URI) and to the global application data namespace. This involves potentially thousands of individual calls in succession.
Functionally, this works as intended - but the performance of these repeated save calls is causing a bottleneck. A couple of questions:
Is there any way that I can batch up multiple
SaveApplicationDatacalls into a single call. I notice the docs mention that multiple
ApplicationDatainstances can be saved at once - so I could at least batch up the global application data into one call. But presumably the subject specific application data will always have to be saved individually?
Is there a more efficient way of storing user-specific data via the core service? I considered creating a new schema field to store this information whilst creating the components - but this application data isn't something that I wish to expose to end users. I'm also loathe to set-up a separate persistence mechanism just for storing this sort of user data.