On Wed, Jun 28, 2017 at 6:53 PM, Colin Putney <colin at wiresong.com> wrote:

>
>
> On Wed, Jun 28, 2017 at 4:15 AM, Bert Freudenberg <bert at freudenbergs.de>
> wrote:
>
>
>> ​Because MC has no concept of "files". Each repository can have a
>> different representation for how it stores a version (e.g.
>> MCDictionaryRepository is literally just a dictionary of MCVersions).
>> That's why an MCVersion is created by an MCReader when loading from a repo,
>> and writing to a repo invokes that repo's MCWriter.
>>
>
> Agreed. How (and whether) MCVersions are serialized is an implementation
> detail of the repository implementation. Early on we expected more
> diversity of repository implementations - Magma, Gemstone, peer images etc.
> There was even a transactional store that got junked shortly before Avi
> started showing people what we were working on. In practice we seem to have
> settled on http and file repositories, so there does seem to be an
> opportunity for optimization. However, even if we make that optimization,
> extensions like TweakMC shouldn't rely on it to be able to function
> correctly.
>

​Colin,

can you imagine how to fit "unknown" definitions into the design? That is,
definitions that are not "understood" by this version of MC, but would
still be preserved somehow, and stored with a new version.

- Bert -​
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20170628/8b8b6458/attachment.html>