Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Applied Materials No-Politics Thread (AMAT) -- Ignore unavailable to you. Want to Upgrade?

To: Cary Salsberg who wrote (2272)	8/11/2002 7:42:15 PM
From: Lizzie Tudor	Read Replies (2) \| Respond to of 25522

<<<RE: "The fact that the client is now thin means more clients can be supported than before..."<<< I don't understand your logic here. A priori, it would seem that the thinner the client, the more support it requires. By "support more clients", I meant support more client types. The no-footprint thin client means you can effectively run SAP on a handheld RF device in your warehouse. Same with all these handheld and wireless gadgets, it used to be they couldn't run the heavy duty enterprise apps, but now they can, since handhelds have enough processing power for the thin clients. My point was the n-tier architecture might enable more points of entry to the enterprise than we had before. Some application vendors are having difficulty with the no footprint model on the client though, its too slow. SAP says they have no footprint, but the sebl users I know say sebl needs a windows accelerator to get the performance they need. Your 3 tiers are just dumb clients attached to servers attached to "backend" data base processing. This is too limited. Umm, not really. I might be misunderstanding your point. The "server" for the middle tier is in itself a layered architecture. It is where the application server runs, and he has his own data layer. He does a fair amount of processing- much more than the old client anyway - But it is not a centralized data store so this one can't be used for say, inventory. But he can be used for personalization and individual data, and some reports. Also content never touches the backend, it is aggregated in the middle tier. I'm not an app server expert but beas oem's oracle and uses a bunch of the object oriented calls for transactional data storage. The back-end doesn't do any OO calls, at least in Oracle 11i (the new app). Lizzie