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
We recently introduced language specific properties, which allows to narrow the scope of properties.
It would be good to have a similar mechanism for "service" specific properties. It doesn't make sense that all C++ applications accept "Glacier2" properties as valid.
We can have a set of "enabled" prefixes, for example Ice, IceSSL should be always enabled and validated.
Others Glacier2, IceGrid, IceStorm should be "reserved" but "disabled", if an application sets such a property its an error.
Then we need a way to enable, the additional prefixes, in which case we validate that the properties are valid.
The text was updated successfully, but these errors were encountered:
We recently introduced language specific properties, which allows to narrow the scope of properties.
It would be good to have a similar mechanism for "service" specific properties. It doesn't make sense that all C++ applications accept "Glacier2" properties as valid.
We can have a set of "enabled" prefixes, for example Ice, IceSSL should be always enabled and validated.
Others Glacier2, IceGrid, IceStorm should be "reserved" but "disabled", if an application sets such a property its an error.
Then we need a way to enable, the additional prefixes, in which case we validate that the properties are valid.
The text was updated successfully, but these errors were encountered: