Microsoft Object Web – the Active Internet Platform (AIP). It is a 3-tier architecture. The first tier belongs to the client. In this case, ...
Microsoft Object Web – the Active Internet Platform (AIP). It is a 3-tier architecture. The first tier belongs to the client. In this case, the client belongs to Sweeper’s OLE-based client components and services. Clients will be access the Internet via componentized browsers – such as Internet Explorer 3.X. A page can contain OLE ActiveXs, Java applets, Visual Basic applets, and regular HTML content. DocObjects can play within browsers or any frame window.
Microsoft’s approach is to rely on digital signatures instead of the language to ensure component safety. To achieve its goal, Microsoft has signed up VeriSign to issue digital signatures for components. A Verisign certificate will ensure that a component has not been tampered with after it leaves the hands of its creator.
You will be able to create OLE document titles using the Microsoft Internet Studio. Once you create a document title, you should be able to upload it to an Internet server by pressing a button; Microsoft calls it “push-button publishing”. The documents will be transported using Internet Files, which is Microsoft’s “cool” name for OLE compound files.
The second client/server tier consists of Microsoft’s Internet Information Server(IIS) , previously known as Gibraltar. IIS bundled with NT Server, which means that it is practically free. IIS will also provide an application framework for running OLE-based business objects. Business objects will also be able to interact with each other using the OLE ORB.
The third tier consists of Microsoft’s BackOffice, and any server application that can be accessed using ISAPI or ODBC. Eventually , Microsoft intends to provide an OLE-based TP-Monitor – called the Component Coordinator – to orchestrate transactions across different resource managers. When this happens, the business objects will become transactional. Microsoft will provide tools for assembling 3-tier client/server Object Web applications. The tools will help you construct both the client and server sides of the Object Web equation.
Microsoft’s approach is to rely on digital signatures instead of the language to ensure component safety. To achieve its goal, Microsoft has signed up VeriSign to issue digital signatures for components. A Verisign certificate will ensure that a component has not been tampered with after it leaves the hands of its creator.
You will be able to create OLE document titles using the Microsoft Internet Studio. Once you create a document title, you should be able to upload it to an Internet server by pressing a button; Microsoft calls it “push-button publishing”. The documents will be transported using Internet Files, which is Microsoft’s “cool” name for OLE compound files.
The second client/server tier consists of Microsoft’s Internet Information Server(IIS) , previously known as Gibraltar. IIS bundled with NT Server, which means that it is practically free. IIS will also provide an application framework for running OLE-based business objects. Business objects will also be able to interact with each other using the OLE ORB.
The third tier consists of Microsoft’s BackOffice, and any server application that can be accessed using ISAPI or ODBC. Eventually , Microsoft intends to provide an OLE-based TP-Monitor – called the Component Coordinator – to orchestrate transactions across different resource managers. When this happens, the business objects will become transactional. Microsoft will provide tools for assembling 3-tier client/server Object Web applications. The tools will help you construct both the client and server sides of the Object Web equation.
