All About Sun Microsystems Message Board

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 : All About Sun Microsystems

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Reginald Middleton who wrote (18957)	8/27/1999 10:07:00 AM
From: Stormweaver	Read Replies (2) of 64865

Here's my two cents: the 'dynamic client' solution... In thinking about this I tried to take into consideration the benefits of thin client (FRU, mobility,lighter client) as well as the industry trend toward faster, cheaper desktop machines. Based purely on industry trends clients should be getting fatter, however the other dynamic is trying to reduce TCO of the desktop. FAT clients are more expensive to manage since they are more complex and offer greater functionality to traditional thin clients (a.k.a dumb terminals). Where we are headed is possibly toward a dynamic client. Here's my rough chicken scratches... 1. Dynamic Resource Probe/Allocation At login/connect time the client/server decide who will be doing what processing based on client resources: processor, memory, disk, network speed. This may change periodically during the session if the aforementioned resources fluctuate outside of expected ranges; ie. net speed goes down. In a true distributed object architecture application objects could reside on the server or client depending on client/server load and resource power. This provides the flexiblity of throttling where the processing is happening. Both client and server have a say in this and in an ideal situation servers could borrow processing power from ideal clients; and vice versa. 2. Storage & Synchronization Again this is dynamic. The client/server determine this but the user also has a say. Therefore depending on the configuration/resources the user may be using the local disk as the primary and the server disk as the secondary. Eventually we blur the idea of client/server. They are all simply network endpoints with resources. p.s. I had too much coffee this morning ! Cheers James

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next