Because this technological area is so complicated, it is unlikely that the average programmer will purchase less than 3-4 books on the subject and spend less than several weeks familiarizing with it. You'll find it enormously easier to internalize and assess more pragmatic texts later on. When I say that an object is activated, I mean that it is either created or fetched from a pool of existing objects. When I say that an object is deactivated, I mean that it is either destroyed or placed back in the pool. Use of JIT activation is mandatory for transactional components.
Nontransactional components can also use it if needed.
In JIT activation, the client creates an object and receives a standard proxy and stub connected by a channel, as shown in figure 3-13. Once the object is created, the client makes calls to it as usual. JIT activation was first presented to the world as a scalability feature for recovering resources. A user-driven client application often creates an object, makes a method call, and holds on to the object for later use. Five minutes or an hour later, the client might make another method call.