Be more storage agnostic

[OlivierChirouze]

We might want to refactor the PAF lib to more storage agnostic and less dependant on cookies.
This implies changing method signatures to manipulate higher level objects.

James, could you please elaborate on that?

Thanks

[jwrosewell]

There is a suggestion in the source code where an update interface is shown.

This method could be expanded to address this issue where there is a common method called "synchronize". The method would work as follows.

1. It is provided optional identifiers and preferences.
2. It then synchronizes with PAF. If a data item provided is newer than the data in PAF then that data is used. If the PAF data is more current then the data provided is discarded.
3. The method then returns the current data.

For example;

1. There is no existing PAF data. No data is passed to the method. The method returns the current PAF data.
2. A new identifier is created that has a newer timestamp than the one in PAF. The PAF value is refreshed and the value provided returned.
3. A new preference value is created from the CMP, but the publisher had an old random identifier. The preference is passed to the method, and the new random identifier and the preference value are returned.

The method could be further abstracted physically so that it always returns a URL that the browser must either.

1. Add as a <script> to the page where 3PC are supported.
2. OR redirect the browser navigation to.

With these two features all abstraction of storage and a single simple interface for synchronisation rather than get / update operations becomes possible.