scispace - formally typeset
Search or ask a question
Author

T. A. Mikalsen

Bio: T. A. Mikalsen is an academic researcher from IBM. The author has contributed to research in topics: Distributed Objects Everywhere & Enterprise JavaBeans. The author has an hindex of 1, co-authored 1 publications receiving 14 citations.

Papers
More filters
Journal ArticleDOI
TL;DR: This paper shows that component models augment each other and proposes how Enterprise JavaBeans can use the additional functions of Component Broker to provide a scalable, transactional, and persistent environment to clients of both worlds.
Abstract: Objects were introduced as programming constructs that encapsulate data and methods. The goal was to foster software reuse and simplify the developer's concept of how a task was implemented. The developer need only know the interfaces to an object to use its functionality. Distributed objects simplified conceptualization further by removing the need to know the locality of an object. Clients invoked methods on distributed objects as if the objects existed in the client's process. Beyond this location transparency, the need arose for distributed objects to survive beyond the life of one client, to be able to support thousands or millions of clients, and to participate in transactions. To support scalability, persistence, and transactional semantics with no dependencies on platform or data store, "component models" were developed. In this paper we look at various component models, focusing on two: IBM's Component Broker and Sun's Enterprise JavaBeansTM. We show that they augment each other and propose how Enterprise JavaBeans can use the additional functions of Component Broker to provide a scalable, transactional, and persistent environment to clients of both worlds.

14 citations


Cited by
More filters
Patent
14 Jun 1999
TL;DR: In this paper, a set of management policies, selectable by the customer at object installation time, is used to manage one or more instances of an object, including at least one of an activation isolation policy, a passivation policy, flush policy, and a refresh policy.
Abstract: A set of management policies, selectable by the customer at object installation time, is used to manage one or more instances of an object. The set of policies includes at least one of an activation isolation policy, a passivation policy, a flush policy, and a refresh policy. The policies are managed by one or more containers of the computing environment.

76 citations

Dissertation
01 Jan 2000
TL;DR: In this paper, the authors adopt a nouvelle demarche for the conception des environnements de tcao, which offre a la fois un support a l'activite cooperative, ainsi qu'un support a meta-activite de redefinition de l'environnement de travail informatise.
Abstract: Dans le domaine de l'informatique, la recherche sur le travail cooperatif assiste par ordinateur (tcao) s'interroge toujours sur la demarche de conception et les fondements a adopter pour enfin creer des collecticiels repondant aux besoins des utilisateurs. Les etudes empiriques tendent a montrer l'invalidite d'une demarche classique de conception qui tente de prevoir a l'avance l'activite particuliere d'un groupe de travail pour l'implementer. En effet, le collecticiel doit pouvoir prendre en compte les besoins emergeants du groupe au fur et a mesure de l'activite. Dans nos travaux, nous avons adopte une nouvelle demarche pour la conception des environnements de tcao. Notre objectif n'est plus de comprendre une activite particuliere pour la modeliser. Nous voulons comprendre ce qu'est l'activite d'une maniere generique, et identifier les concepts et mecanismes fondamentaux qui la caracterisent de maniere a directement les rapprocher des fondements informatiques utiles a la conception. L'etude de la theorie de l'activite (at) nous a permis de specifier une certaine vision des collecticiels, et d'en proposer une realisation nommee dare (activites distribuees dans un environnement reflexif). Cette realisation offre a la fois un support a l'activite cooperative, ainsi qu'un support a la meta-activite de redefinition de l'environnement de travail informatise.

60 citations

Patent
14 Jun 1999
TL;DR: In this paper, the management functions typically performed by containers of a server instance are delegated to resource managers coupled to the server instance, such as locking, security control, multi-system caching and commitment control.
Abstract: Management functions typically performed by containers of a server instance are delegated to resource managers coupled to the server instance. For example, responsibility for such management functions as locking, security control, multisystem caching and commitment control are removed from the containers and delegated to the resource managers. This enables ongoing improvements and functional extensions provided in the underlying resource managers to be immediately leveraged transparently in the server instance.

60 citations

28 Sep 2014

57 citations

Patent
14 Jun 1999
TL;DR: A transactional name server as mentioned in this paper is a name server that provides a local interface to a directory service that propagates a transactional context from the name server through a directory down to a resource manager.
Abstract: A transactional name server. One or more objects of the name server are managed as transactional objects, thereby providing a transactional name server. Atomic updates are provided in the name server by the addition of transactional semantics. The transactional semantics include making the objects of the name space managed objects and providing a local interface to a directory service that propagates a transactional context from the name server through a directory down to a resource manager.

53 citations