| 5 | | To support this feature we will introduce the concept of ''submodel''. A ''submodel'' is just a normal model whose data is related to a parent model. For example, we will be creating a new model called ''serverAliases'', this model will behave as a ''submodel''. For every virtual host, that is, for every row in the ''VirtualHosts'' model we will associate another model of ''serverAliases''. Or to put it another way, every row of ''VirtualHosts'' has many ''serverAliases''. In practice this means a few things, amongst them: configuration data is stored in a tree or directory structure, so submodel data will live under its parent model directory. |
| | 5 | To support this feature we will introduce the concept of ''submodel''. A ''submodel'' is just a normal model whose data is related to a parent model. For example, we will be creating a new model called ''serverAliases'', this model will behave as a ''submodel''. For every virtual host, that is, for every row in the ''!VirtualHosts'' model we will associate another model of ''serverAliases''. Or to put it another way, every row of ''!VirtualHosts'' has many ''serverAliases''. In practice this means a few things, amongst them: configuration data is stored in a tree or directory structure, so submodel data will live under its parent model directory. |
