The Thin Technology demands for more and more compact native x86 platforms optimized for more and more productive applications. By measuring just 4.71 x 5.21 x 2.68 inches in dimension, Enjay MiniPC could be an ideal choice to be used as a Thin Client. Adding to this, the extra-ordinary feature of just 15 watts of power consumption can cut down the power consumption by 85 to 96 percent as compared to power consumption of a normal PC cabinet.
Moreover, having all the features of a normal Enjay Thin Client Product, Enjay Mini PC, is a perfect platform for a wide range of commercial solutions. Its high bandwidth connection is supported by 3 USB host connections and the 10/100 Ethernet network interface with PXE boot from LAN option.
Enjay Mini PC is fully compatible with Microsoft® Windows and Linux Operating System. In addition it also has a support for Windows CE and Windows XP Embedded OS.
Showing posts with label enjay. Show all posts
Showing posts with label enjay. Show all posts
Thursday, May 10, 2007
Monday, April 9, 2007
1000 MBPS Thin Client
Have you ever wondered why non of any big Thin Client vendors have yet launched 1 Gbps Thin Client.
Well, the reason is quite obvious, and that is the Thin Client technology itself.
Thin Client technology works on following BASIC PRINCIPLES:
1. Keystrokes and Mouse movements are sent from the
CLIENT to the SERVER PC.
2. The Server does ALL THE PROCESSING, on behalf of CLIENT.
3. Then SERVER send "BITMAP IMAGE" of the screen for the
client.
From above Principles you can draw following conclusions.
1. If you Open "a 500 MB file" on a thin client
PC, 500 mb is not going to FLOW FROM SERVER TO CLIENT.
2. It is only images of the apps that will flow from
the SERVER to the CLIENT machine.
3. ONE OF THE MAJOR BENEFITS OF THINCLIENT TECHNOLOGY
IS "VERY VERY LOW REQUIREMENT OF BANDWIDTH"
4. This is the reason, when people want to use
applications in WAN Connectivity, they use
Thin Client technology.
We are not even using 100 mbps:
-------------------------------------------------
Yes that is true, when we use ThinClients
We generally use 20-200 kbps "YES KBPS"
Actually Network bandwidth is not bottleneck for
ThinClient Technology. BottleNeck may be your SERVER.
So if you want MORE SPEED, GET FASTER SERVER.
So if someone is telling you speed of ThinClient
is better because of 1GBPS, then,
NOTHING CAN BE MORE FAR FROM TRUE, than this.
Pl. understand the technology before using / buying selling it.
If you spend some time to understand it, you will end up using
It much better and efficiently.
If you any doubts / queries regarding above, pl. write to me
I WOULD LOVE TO DISCUSS (OR DEBATE) ON THIS issues.
Well, the reason is quite obvious, and that is the Thin Client technology itself.
Thin Client technology works on following BASIC PRINCIPLES:
1. Keystrokes and Mouse movements are sent from the
CLIENT to the SERVER PC.
2. The Server does ALL THE PROCESSING, on behalf of CLIENT.
3. Then SERVER send "BITMAP IMAGE" of the screen for the
client.
From above Principles you can draw following conclusions.
1. If you Open "a 500 MB file" on a thin client
PC, 500 mb is not going to FLOW FROM SERVER TO CLIENT.
2. It is only images of the apps that will flow from
the SERVER to the CLIENT machine.
3. ONE OF THE MAJOR BENEFITS OF THINCLIENT TECHNOLOGY
IS "VERY VERY LOW REQUIREMENT OF BANDWIDTH"
4. This is the reason, when people want to use
applications in WAN Connectivity, they use
Thin Client technology.
We are not even using 100 mbps:
-------------------------------------------------
Yes that is true, when we use ThinClients
We generally use 20-200 kbps "YES KBPS"
Actually Network bandwidth is not bottleneck for
ThinClient Technology. BottleNeck may be your SERVER.
So if you want MORE SPEED, GET FASTER SERVER.
So if someone is telling you speed of ThinClient
is better because of 1GBPS, then,
NOTHING CAN BE MORE FAR FROM TRUE, than this.
Pl. understand the technology before using / buying selling it.
If you spend some time to understand it, you will end up using
It much better and efficiently.
If you any doubts / queries regarding above, pl. write to me
I WOULD LOVE TO DISCUSS (OR DEBATE) ON THIS issues.
Subscribe to:
Posts (Atom)