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
This was a thought very early in the life of properties, but nothing has come of it. The idea is that properties may become an interface for a database, where underlying property values are stored somewhere a bit more robust than just a dictionary.
In practice, though, properties has worked well as a user interface separated from the database by serialize/deserialize. The close connection of _backend to a database has not been necessary.
Is there any merit to the idea of "swappable backends"? My current thinking is "no" but maybe there is.
The text was updated successfully, but these errors were encountered:
This was a thought very early in the life of properties, but nothing has come of it. The idea is that
properties
may become an interface for a database, where underlying property values are stored somewhere a bit more robust than just a dictionary.In practice, though,
properties
has worked well as a user interface separated from the database byserialize
/deserialize
. The close connection of_backend
to a database has not been necessary.Is there any merit to the idea of "swappable backends"? My current thinking is "no" but maybe there is.
The text was updated successfully, but these errors were encountered: