I noticed that the API now returns two undocumented items on a profile: parent_unions and partner_unions.
1) Is this a step on removing the need for the immediate-family record?
2) Will partner_unions replace the unions element?
What I am missing most in getting an effective caching of loaded profiles is that there is absolutely no way to detect changes in a profiles connections (i.e changes in parents, children, spouses), so you cannot cache immediate-family records.
3) Will any changes in the parent_unions or partner_unions solve this problem by updating the updated_at element on a profile?
I also notice that a lot of elements in v0 of the API like big_tree now is marked with "This field has been deprecated and will no longer be supported in the future versions".
4) Does this mean that those elements will be removed for v1 as well?
Kenneth, - you only need to load immediate-family records when following a line since immediate-family also contains the profile records, so parent_unions is not needed, but as you say: you have an overload since you also get all spouses and siblings, but that is needed if you want to process a descendants line.
I am able to load 10 generations of ancestors in 29 seconds now and I am not finished fine tuning my code yet.