- Main Page
- Namespaces
- Classes
- Files
- Related Pages

- Search for |

# Implementation Repository

### 1.5.1

-*- HTML-Helper -*-

Id
  README.txt,v 1.17 2005/05/23 17:58:34 michel_j Exp

## Introduction

The purpose of the Implementation Repository (ImR) in TAO is for the automatic activation of a TAO server when a method is invoked but the server is not running. It does this by working with the server to keep track of when it is activated and stores information on how to reactivate it. Method invocations on the server will actually be sent to the Implementation Repository, which will then be able to start the server process if it is not already running and forward the invocation to the real server.

## Resources

The ImR in TAO was first based on a paper on the subject by Michi Henning called Binding, Migration, and Scalability in CORBA. Mr. Henning later went on to coauthor the book Advanced CORBA Programming in C++ and included a chapter on the Implementation Repository. The description of the ImR in this chapter is used as the specification for TAO's ImR.

Implementation Repository User's Guide - Overall documentation on how to use the ImR in your programs

Future Work - Future Work

Running as an NT service - Running the ImR as a NT Service

Naming Service - Using the Naming Service with the Implmentation Repository

Transition from IMR in TAO 1.2.2 - Moving from IMR as in TAO 1.2.2 to the present version.

## Authors

The guy who first worked on ImR and provided a base for the current ImR is Darrell Brunsch <brunsch@cs.wustl.edu>. The current version is developed by Priyanka Gontla <gontla_p@ociweb.com>. You can reach us by either email (which is better), or through the ACE mailing list <ace-users@cs.wustl.edu>, or through the comp.soft-sys.ace newsgroup. The newsgroup mirrors the mailing list, but not the other way. Also, if you use the mailing list, it is best if you join it before sending a question since responses are usually just replied back to the group.

The NT Service part of the ImR was developed by Jeff Parsons <parsons@cs.wustl.edu>. He can also be reached via the same channels. It was later extended and enhanced by Justin Michel <michel_j@ociweb.com>