[hand with pencil]
Stuff For Sale
2004 Summer Tour
About
Blog
Class Stuff
Email Me
Events
Gallery
Home
In The Press
Newsletter
Services
Smalltalk
Veggie Van Gogh

Credits
© 2002,
Bytesmiths

[this is simply a banner and menu bar]

Please patronize sponsors of this page!

Bytesmiths no longer is involved in software consulting. Maintenance of this web site is currently subsidised by unrelated business activities. Please pass the word to other interested folks, so I can continue to host this page!
Your site could be listed here, for as little as $12 per month! Go to Bytesmiths Press for details.

This site has been selected by PC Webopaedia as one of the best on this topic!
This site has been awarded a Links2Go Key Resource Award in the Smalltalk category!

[ prev | top | next ]

Shared Repository

(This is a slide show. You really won't get 
anything out of it unless you have a graphical web browser with graphics turned 
on.)

Repository

  • The repository is an OTI proprietary database. On UNIX systems it is managed by a process called emsrv , which runs on the server with the repository. Each user image is connected to the repository when the image is started up.

  • Since it is a database, there are some fields that are under developer control. One can create a user field for applications, for example, that enable you to store drawings as part of the documentation for the application.

Concurrent development

  • When a developer saves a new version of a method, you can see it immediately, and load it into your image. This is also true for new versions of classes, and other software components.

  • Unless specifically restricted by an application manager, any developer can work on any class in any application.

  • There are controls that prevent these "conflicting" versions of classes from being harmful; indeed they are often desirable.

  • No change made by another developer affects your image until you load the code.

Atomic Loads/Unloads

  • Loadability analysis is performed before load is attempted.

  • You no longer have the equivalent of a file-in that "breaks in the middle" (for exception, see ENVY Advanced Topics).

  • Classes and Applications can be atomically unloaded from your image. Unloadability analysis is performed before unload begins.


    [ prev | top | next ]