Re: Re: Re: Modify the IE Browser

> From: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
> Back on the old System/3, we had something called a
> NEP-MRT (Never Ending Program, Multiple Requesting
> Terminals).

It's funny that technology recycles while reaching upward toward higher
plateaus.

With thin client architecture, the server maintain state.  With thick client
architectures, the client maintains state.  Browsers offer a middle ground
where state might be shared.

The task swapping example I referenced in a previous message illustrated
that the browser could maintain the state of a an embedded ActiveX
component, along side a panel containing a frame with an HTML page.  The
browser window can be something of a control center, allowing swapping
between activities, but where activities are controlled by the server.

Nathan M. Andelin
www.relational-data.com