| J. Waldo. Jini Architecture Overview. Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, CA 94303, 1998. http://www.javasoft.corn/products/jini/index. html |
....group at University of Karlsruhe is on improving the protocol interoperability between ubiquitous computing devices and traditional distributed systems. The research group has developed an open architecture for integrating a wide range of communication protocols [7] such as Inferno [16] JetSend [17], Jini [18] Salutation [19] Tspaces [20] and UpnP [21] The primary focus in this project is to provide an abstraction over several communication protocols. The code mobility features of the JUCE infrastructure also provide protocol level interoperability. For instance, such an infrastructure ....
J. Waldo. Jini Architecture Overview. Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, CA 94303, 1998. http://www.javasoft.corn/products/jini/index. html
....in the Internet. It defines multiple name spaces, and also designs name resolution mechanisms for various objects. However, since the design of URI URN is highly dependent on DNS architecture, it is unclear whether it would work well in the ubiquitous Internet. Middleware platforms, such as Jini [8], UPnP (Universal Plug and Play) 9] or HAVi (Home Audio Video interoperability) 10] usually contain a directory service. However, these directory services are not designed for a global area network. Moreover, none of them clearly defines naming schemes. 3. Service Synthesizer on the Net As ....
J. Waldo, "Jini Architecture Overview", Sun Microsystems Inc., 1998.
....and o ers a conventional OS view of processes. 2K is divided along lines of service at a 22 higher level of abstraction, namely distributed resource managers with QoS support, distributed global naming, and o ers a distributed mobile execution environment view. Systems such as Ninja [5] and JINI [22], look at leveraging basic Java technologies. They share with 2K universal connectivity and automatic con guration. While Ninja and JINI focus on bridging the gap between high end servers and small devices, 2K aims at adapting the user s varying requirements to the underlying platform features. ....
J. Waldo. Jini architecture overview. http://www.sun.com/jini/overview.
....the organizations of NASA and its partners. This requires tools for specifying memory requirements, the number of distributed processes, processing speeds, compilers, wall clock time needs, libraries, header files, and so on. 2.2. Globus metacomputing toolkit Several recent research projects [1, 5, 8, 15] provide prototypes for the IPG Virtual Machine layer. In this paper we test one of them, the Globus metacomputing toolkit [5] as a possible realization. Globus evolved out of the successful but still somewhat ad hoc I WAY high performance distributed computing experiment [4] Globus provides ....
J. Waldo. Jini architecture overview. Sun Microsystems, 1998; http://java.sun.com/products/jini/whitepapers.
....of storage devices; humans do not have to worry where to put what. Their prototype system is capable of assigning several thousands of objects to devices in a few minutes. Sun s Jini makes devices, including disks, identify themselves as part of their automatic component discovery paradigm [Wal98] The devices either have enough intelligence built in them 9 to be able to identify themselves to the clients, or they will download the drivers from a server. There is also a recent project in Sun called Jiro, which defines a storage management interface to let components manufactured by ....
....data involves keeping track of where everything is located, reallocating space as necessary, and so on. Although it is an interesting research field, there are other projects that are pursuing it and I did not think we could make my approach generic enough to be of a wide interest 35 [BGM 96, Wal98, Jir99] For a summary of other research projects on this topic, please refer to Section 1.3.4. 4.1 Self Maintaining System In this section, I will define what self maintaining means, and outline the requirements on how to construct such a system. 4.1.1 Definition of Self Maintaining System ....
Jim Waldo. Jini architecture overview. Technical report, Sun Microsystems, 1998. white paper.
....authority. Here, we should mention the emerging Web Interface Definition Language (WIDL) 34] Based on XML [35] WIDL defines interfaces to Web data and services, enabling automatic and structured Web access by compatible client programs. Finally, the recently announced Jini technology [36], together with JavaSpaces, promises a flexible and easy to use set of components for federating services in a distributed system. In this respect, Jini and JavaSpaces technologies may soon prove more powerful for Internet based distributed applications, although they mainly focus on the ....
....it is necessary that the service invocation interface is described in an appropriate language and that this description is accessible to the responsible execution agent. Suitable languages for (remote) service invocation are CORBA s IDL [27] Java s RMI [31] and the recently announced Jini [36] and JavaSpaces [21] technologies, or WIDL [34] each of them with specific advantages and tradeoffs. We believe, however, that WIDL is the most appropriate candidate because it imposes the fewest constraints on the use of legacy software. Finally, there is a need to describe the desired behavior ....
J. Waldo, "Jini Architecture Overview", White Paper, Sun Microsystems Inc., Palo Alto, USA, 1998. http://java.sun.com/products/jini/whitepapers/
....networks that may scale globally, and managing resources by freezing and thawing objects when needed. This research is more focused on organizing dynamic groups of people. Jini technology enables heterogeneous devices equipped with a Java virtual machine to discover services in physical spaces [34]. Devices may register themselves with the Jini lookup service. One registered, other devices may discover them and immediately use their services. Using the code mobility of Java, custom user interfaces or application may be sent to client devices to allow interaction with services or resources. ....
Jim Waldo. Jini Architecture Overview. http: //java.sun.com/products/jini/whitepapers.
....uiuc.edu ActiveSpaces DeviceFramework. 3 Conclusion The recent progress in hardware technology is enabling the construction of active spaces with thousands of embedded devices, which augment our perception of reality with new dimensions. Despite recent advances in software technology like Jini [Wal98] existing operating systems and 6 middleware are not yet prepared to manage such complex environments. They exhibit intricate dependencies and strict requirements with respect to interoperability, automatic con guration, security, privacy, fault tolerance, and quality of service. In the 2K and ....
Jim Waldo. Jini Architecture Overview. Available at http://java.sun.com/ products/jini/whitepapers, 1998.
....in that they also often introduce a hierarchy of resources and provide some functionality (i.e. operations for search, reservation and acquisition of resources) Resource models in this domain, however, seem to lack the flexibility and generality that we need. The Jini distributed software system [16], which is currently being developed by Sun Microsystems, employs a resource modeling approach somewhat similar to ours. The Jini system is a distributed system based on the idea of federating groups of users and the resources required by those users. The overall goal of the system is to turn a ....
J. Waldo. Jini Architecture Overview. Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, CA 94303, 1998. http://www.javasoft.com/products/jini/index.html.
....Bob s phone was able to discover the stereo system, retrieve its interface, and pause the music. Resource discovery is the subject of numerous research efforts including the RDP [27] and SLP [25] protocols, Berkeley s Service Discovery Service [5] Sun Microsystems JavaSpaces and Jini [34], T Spaces from IBM [29] Universal Plug and Play from Microsoft [28] and the HAVi consumer electronics consortium [14] Each takes a slightly different approach based on the application domain they were intended for. None were designed specifically with mobile networks in mind, so a host of ....
J. Waldo. Jini architecture overview. Technical report, Sun Microsystems, Inc., Palo Alto, CA, 1998.
....be customized to suit a specific need. The Java model is key to opening up convenient user interaction with all forms of embedded computation. Being able to interact with an appliance is only half the battle, the other half is knowing the types of appliances and services that are at hand. Jini [9] is an example of a discovery service and was invented to enable local appliances, or services, to be located by client processes in order to form ad hoc communities of devices that can communicate and benefit from mutual interaction. A Jini lookup service runs on a local server and acts as a ....
Waldo J., "Jini architecture overview". Technical report, Sun Microsystems, Inc., Palo Alto, CA, 1998.
....adaptive policies. 5. Related Work There are a number of contributions to distributed operating systems environments, each of them emphasizing di erent aspects of the problem. We discuss some representative cases such as Ninja, JINI, EJB, Globus and Legion. Systems such as Ninja [4] and JINI [12], look at leveraging basic Java technologies. They share with 2K universal connectivity and automatic con guration. While Ninja and JINI focus on bridging the gap between high end servers and small devices, 2K aims at adapting the user s varying requirements to the underlying platform features. ....
J. Waldo. Jini architecture overview. http://www.sun.com/jini/overview.
....within her visual eld. The anesthesiologist and the nurse have their own environments with their own visual displays. The environment of the operating room includes all the devices running in the room and relevant to the surgery, including those monitoring the patient. Figure 1(a) depicts the UML [16] class de nition of an environment. Environment env id: Environment parent: Environment profile: Profile state: StateType statistics table: StatTable protection domain: ProtectionDomain credentials table: CredentialsTable container table: ContainerTable component table: ComponentTable ....
J. Waldo. Jini architecture overview. http://www.sun.com/jini/overview, 1998.
....Continuous availability needs runtime reconfiguration, which leads to dynamic systems. Mobile Computing is the discipline of mobile computing devices or mobile code, which leads to the same key issue: a running system has to adapt dynamically to a changing environment. New middleware like JINI [Wal] or Salutation [Con] are offering first concepts on a technical level. Their middleware is automatically adapting to changes in the environment and therefore offer a transparent layer to the application (see figure 1 ) However, there is no adequate development methodology, that covers the ....
....and their set of components during runtime dynamic systems. Figure 3 shows two possible configurations for one dynamic system: The relations between the component types stay fixed, but the relations between the instances may vary. Examples for those kinds of middleware are CORBA 3. 0, JINI [Wal, FSS00a],WAP, Millenium[Cor] Inferno, GLOBE etc. This is done by specifying common lookup services and object migration facilities, that allow to find a needed component, eventually migrate it to the needed location and adapt it to the specific environment. A special case of dynamic systems are mobile ....
Jim Waldo. Jini architecture overview. http://java.sun.com/products/jini/whitepapers/architectureoverview.pdf.
....Internet services with diverse small devices. CORBA [40] and DCOM [14] provide platform independent, object based network communication, although both systems are designed for tightlycoupled distributed applications and do not directly support composition and aggregation of components. Jini [39, 43] takes a Java centric view, exploiting bytecode mobility to deliver stub code which implements a private communication protocol between client and service; stubs export a programming model based on Remote Method Invocation (RMI) 38] Although Jini s literature describes a holistic distributed ....
Jim Waldo. Jini Architecture Overview. Available at http: //java.sun.com/products/jini/whitepapers.
....of an emphasis on shared objects. Mocha, like Aleph, provides the ability to run threads at di erent nodes, and to share objects among those threads, without modi cations to the JVM. Mocha provides a substantially di erent API, with an emphasis on fault tolerance and replication. The Jini system [28] provides Java based support for distributed systems with a focus on federating distinct services. JavaParty [15] provides language support for remote objects and threads. ....
J. Waldo. Jini architecture overview. www.javasoft- .com/products/jini/whitepapers/index.html, 1998.
....and terminals and o ers a conventional OS view of processes. 2K is divided along lines of service at a higher level of abstraction, namely distributed resource managers with QoS support, distributed global naming, and o ers a distributed mobile execution environment view. Other systems, like JINI [14], look at leveraging basic Java technologies. JINI o ers services, as collections of objects written in Java, that can be federated to accomplish a task. Services communicate through protocols, such as discovery and lookup; lookup for invocation or location of a service and discovery for ....
J. Waldo. Jini architecture overview. http://www.sun.com/jini/overview, 1998.
....software life cycle, i.e. to be able to change the composition of the component during design, binding and runtime (see figure 1) We claim that today the technological infrastructure is getting to a stage where these kind of applications becomes a reality. New dynamic middleware like Sun s Jini[Wal] or the specification of CORBA 3.0[OMG] seem to confirm this position: the allocation and binding of components is done dynamically by the middleware and the wiring between the components isn t fixed. So components may be dropped, rearranged and recombined during runtime. This clearly shows a ....
....define the types of changes. We believe that the demand in dynamic and mobile features for distributed systems will increase in the near future. The enforced efforts of almost all major IT companies (SUN, Microsoft, HP, Lucent) in developing self adapting distributed component platforms like Jini[Wal] or Millennium [Cor] seems to confirm our position. However, making the technique available by providing a platform seems not to be enough to guarantee high quality software. Concepts to develop, describe and categorize dynamic architectural changes are required. Most of all, the problem of ....
Jim Waldo. Jini architecture overview.
....as this transformation is, we believe that a potentially deeper transformation is on the horizon. Today, users access services from desktop machines. Current trends, however, indicate that in a not too distant future, networked computing appliances will become a pervasive part of our environment [5, 18, 19, 25]. 1 Environments with embedded devices are likely to be permeated with network services they would need to be if they are to achieve their full potential. The ability to access services in situ is likely to catalyze entirely new classes of services. For example, an information aggregation ....
....Service modules written in a stream based model are usually easier to plug together and to reuse as the interactions between such modules are limited to explicitly named channels. Another major thrust for building network services is based on distributed object systems such as CORBA [8] and Jini [25]. The key idea behind this approach is to develop service components with well defined interfaces instead of monolithic services. These components can discover each other using a ubiquitous lookup infrastructure and can interact with each other to provide the higher level services desired. Since ....
J. Waldo. Jini architecture overview. http://www.sun.com/jini/whitepapers/architecture.pdf, 1999.
....typed interface on these components (including carefully chosen data structures that precisely describe the contents of the Jukebox) and the use of soft state to achieve eventual consistency in the Jukebox. Disciplined use of a distributed component architecture: as exemplified by Sun s Jini [21] and Corba [20] distributed component architectures advocate the use of an object oriented language to decompose applications into smaller, self contained objects, and the distribution of those objects across machine boundaries, relying on mechanisms such as RPC to perform inter object ....
Jim Waldo. Jini Architecture Overview. Available at http://java.sun.com/products/jini/ whitepapers.
....of a popular search engine service, or to move the service into a new environment these sorts of modi cations would take massive engineering e ort. Emergent services in a world of distributed objects: this strategy is just beginning to become popularized with architectures such as Sun s JINI [31] and the ongoing CORBA e ort [25] In this world, instead of erecting complex, in exible services, large numbers of components or objects are made available over the wide area, and services emerge through the composition of many such components. This approach has the bene t that adding to the ....
....in Java by deallocation , we mean discarding all references to an object, thus enabling it to be garbage collected. 8 VIA is the Virtual Interface Architecture [26] which speci es an industry standard architecture for highbandwidth, low latency communication within clusters. Sun s JINI [31] architecture is similar to the the Base architecture in that it proposes to develop a Java based lingua franca for binding users, devices, and services together in an intelligent, programmable Internet wide infrastructure. JINI s use of RMI as the basic communication substrate and use of code ....
Jim Waldo. Jini Architecture Overview. Available at http://java.sun.com/products/jini/ whitepapers.
.... to persistently log messages for off line debugging. ffl DebugOutputMessager send messages via a JMS conformant messaging infrastructure to a some remote objects. ffl DebugOutputRemoteEventSource to provide debugging messages as distributed events (perhaps as part of a Jini[7] application) ffl DebugOutputScrollableWindow display messages in an independent, scrollable window. ffl DebugOutputServletLog to persistently log messages via the servlet developers kit s debugging interface. ffl DebugOutputSpace store debugging events in a JavaSpace[6] Finally, ....
Jim Waldo. Jini Architecture Overview. Sun Microsystems, Inc., 2550 Garcia Ave. Mountain View, CA 94043, 1998.
....fails to respond to the component being destroyed. This can be addressed by assigning an expiration time to the validity of the rei ed dependencies between components. This mechanism is known as leases [GC89] and is also used in other contexts like the SODA distributed le system [KM95] and JINI [Wal98] After a lease is expired, a component may assume that the dependency no longer exists and complete its destruction process. In this case, a component that relies on a particular dependency must always verify if the lease for this dependency is still valid. Alternatively, a timer can be set for ....
Jim Waldo. Jini Architecture Overview. Available at http://java.sun.com/ products/jini/whitepapers, 1998.
....are Java based agent architectures primarily directed towards building mobile agents (agents that move from machine to machine during execution) While JGram agents may send executable code to each other for remote execution, this is not explicitly supported by the current framework. Sun s JINI [19] promises several exciting enhancements, particularly in the area of hardware interfaces; we hope to exploit some of these features in future versions of the JGram framework. In summary, the JGram framework is specialized towards the needs of particular multi agent systems (those easily expressed ....
Waldo98. Jini architecture overview. Technical report, Sun Microsystems, July 1998. <http://- java.sun.com/products/jini/whitepapers/architectureoverview.pdf>.
No context found.
Jim Waldo, Jini Architecture Overview, Sun Microsystems, 1998. http://java.sun.com/products/jini/whitepapers/architectureoverview.pdf
First 50 documents
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC