You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://github.com/openpolis/poplus-pci takes a "no-database" approach for composing different components. SayIt takes a "master-slave" approach: it treats a PopIt instance as the master, and doesn't push any edits to speakers to PopIt. Should there be an option to have SayIt operate using a "no-database" approach for speakers, i.e. SayIt only stores the PopIt identifier for a speaker, and when speaker data is needed, it queries the PopIt instance, like poplus-pci?
https://github.com/openpolis/poplus-pci takes a "no-database" approach for composing different components. SayIt takes a "master-slave" approach: it treats a PopIt instance as the master, and doesn't push any edits to speakers to PopIt. Should there be an option to have SayIt operate using a "no-database" approach for speakers, i.e. SayIt only stores the PopIt identifier for a speaker, and when speaker data is needed, it queries the PopIt instance, like poplus-pci?
/cc @guglielmo
The text was updated successfully, but these errors were encountered: