• All in the Memory -- bookkeeping services
• Arabella -- a dynamic musical duo
• Bytesmiths Editions -- large, archival, fine-art photography on unusual materials
• Bytesmiths Press -- artists' services: web design/hosting, jury slides, giclee reproductions, opening announcements, brochures, etc.
• Champagne Beadworks -- handcrafted jewelry and beadwork
• Crafted By Carol -- handcrafted jewelry and beadwork
• Dana Fontaine -- unique photography-derived art
• Dymond Graphics -- note cards, pet/people photography
• Fountains & Funktini -- glass art and more from Beth Keenan and JoAnn Rawley
• Gemini Gypsy -- Carole Good-Hanson's fused glass frames
• Mary Kollman Fine Art -- lovely floral watercolor originals
• Primrose Studio -- terra cotta switch plate covers and wall art
• Ratso's Studio -- astoundingly realistic bronze sculpture
• The Spiral Gallery -- local artists exhibit in the Oregon Cascades foothills
• The Roaming Artist -- info and resources for artists "on the road"
• Van Dyke Sepias -- Jan Van Dyke's nostalgic sepia toned photography
• Veggiemog -- life and times of Kelly O'Toole's Unimog, running on biodiesel
• Village of Willamette Arts Festival -- annual visual/performing arts festival, third weekend of September
• Whitehorse Designs -- Gwen Miller's beadwork and fused glass
• West Linn Arts Commission -- city support for the arts

Shared Repository

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.

• 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.

• 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 ]