This Object web is very similar to Microsoft’s Object Web, except that all the technologies are based on open standards. The open Object W...
This Object web is very similar to Microsoft’s Object Web, except that all the technologies are based on open standards. The open Object Web is also a 3 tier Client/server architecture. The first tier belongs to the client. In this case, the client belongs to Java components, ORBlet’s, OpenDoc compound documents, and shippable places.
Clients will be able to access the Internet via componentized browsers; for example, Cyberdog or a future version of Netscape. In addition to ordinary HTML pages, the browser will be able to play OpenDoc titles. A title is a shippable place; it will be able to contain ActiveXs, OpenDoc parts, Java applets, and regular HTML content.
The second tier will be provided by any server that can service both HTTP and CORBA clients. This combination is supported on almost every server platform-including Unixes, NT, OS/2, Netware, Mac, OS/400, MVS, and Tandem Nonstop Kernel. CORBA objects act as a middle tier; they encapsulate the application’s business logic. They interact with client components via a Java ORBlet or any regular CORBA ORB that can run IIOP(Internet – Inter ORB protocol) over the Internet. They can also talk to existing server applications in the third tier using SQL or any other form of middleware.
The third tier is almost anything a CORBA object can talk to. This includes TP Monitors, MOMs, DBMSs, ODBMSs, Lotus Notes, and e-mail.
In a CORBA/OpenDoc Object Web, the second tier also acts as a store of component titles and shippable places. These can be stored in shippable Bento files that are managed by an ODBMS or DBMS.
Clients will be able to access the Internet via componentized browsers; for example, Cyberdog or a future version of Netscape. In addition to ordinary HTML pages, the browser will be able to play OpenDoc titles. A title is a shippable place; it will be able to contain ActiveXs, OpenDoc parts, Java applets, and regular HTML content.
The second tier will be provided by any server that can service both HTTP and CORBA clients. This combination is supported on almost every server platform-including Unixes, NT, OS/2, Netware, Mac, OS/400, MVS, and Tandem Nonstop Kernel. CORBA objects act as a middle tier; they encapsulate the application’s business logic. They interact with client components via a Java ORBlet or any regular CORBA ORB that can run IIOP(Internet – Inter ORB protocol) over the Internet. They can also talk to existing server applications in the third tier using SQL or any other form of middleware.
The third tier is almost anything a CORBA object can talk to. This includes TP Monitors, MOMs, DBMSs, ODBMSs, Lotus Notes, and e-mail.
In a CORBA/OpenDoc Object Web, the second tier also acts as a store of component titles and shippable places. These can be stored in shippable Bento files that are managed by an ODBMS or DBMS.
