Shopping Cart

VirtueMart

Your Cart is currently empty.

Live Support

bestdelldeals_web

bestdelldeals_web

Home Tech Blog The Register
The Register
FTP celebrates ruby anniversary PDF Print E-mail
Written by Urszula   
Saturday, 16 April 2011 15:31

File Transfer Protocol (FTP) marks its 40th anniversary on Saturday (April 16).

The venerable network protocol was first proposed by Abhay Bhushan of MIT in April 1971 as a means to transfer large files between disparate systems that made up ARPANet, the celebrated forerunner to the modern interweb.

The protocol required a minimum of handshaking, and even more crucially was tolerant of temporary interruptions during long file transfer sessions, making it far more suitable for the job than anything available at the time or HTTP, which came years later.

Last Updated on Saturday, 16 April 2011 15:34
Read more...
 
UK is 15th best place in the world to do IT PDF Print E-mail
Written by Urszula   
Wednesday, 13 April 2011 13:48

Still better than France, though. And Australia

Blighty has been ranked as the 15th best country in the world in which to try to make use of Information and Communications Technology (ICT). Sweden is top, just barely pipping Singapore to the post, and other Nordic and Asian Tiger nations dominated the top 10.

Read more...
 
My desktop is always there for me PDF Print E-mail
Written by Urszula   
Tuesday, 12 April 2011 11:54

High availability loveliness

Desktop virtualisation can be an asset to an organisation, but what happens when something goes wrong? In a conventional non-virtualised desktop system, users with a downed network or crippled server could perhaps still work on something locally.

But when that same downtime means that your whole desktop vanishes, high availability becomes even more important. How can we keep the virtual desktop up and running?

For the naysayers, it's worth pointing out that, done well, desktop virtualisation provides a higher level of disaster recovery than local desktops. Even in mid- to large-sized enterprises where IT is more locked down, many PCs may not be backed up.

Alternatively, with a VDI system, at least the system is available centrally if the desktop device gets fried. "You can connect via a network to the last session that you had, and it's easy to recover. All you're doing is connecting to the session, with the data and the applications," points out Mike Osborne, managing director of ICM, a business continuity provider, adding that this can get individuals up and running faster than before in the event of a desktop crash.

The other upside to VDI is that it enables home working. "What you're talking about is the ability to enable 100 per cent of an organisation's resources in a disaster instantaneously," he says. That assumes, of course, that you can get corporate telephony out to the remote desk, too.

Different strokes

Erwin Vollering, service director of virtualization at Glasshouse Technologies, a cloud services provider, starts by asking what the client's uptime requirements are. You'll often find that different departments have different requirements, he explains.

"For some, it needs to be available 24 x 7, no matter what," he says. "Then we look at a solution where we can facilitate that, in which certain brokers can do that for user groups that have a higher need than others."

When this is ascertained, the implementation team needs to assess every link in the chain between the desktop client and the back-end virtual machine. This includes the network connection from the desktop to the data centre, or wherever the virtual machines are being hosted. It includes home users' gateways, routers, firewalls, and SSL VPN concentrators. Even the hypervisor has to be designed for extra capacity for failing over from another box.

Synchronising a storage area network is difficult enough, but even synchronising locally stored data on the server between different hypervisors can be tricky. Part of the problem is taking a variety of different desktop images, and synchronising them along with the user data that also has to be available.

"If you're using stateless desktops with a profile virtualisation solution, the amount of data you need to keep in sync between sites can be reduced," says Russell Raynsford, managing director of infrastructure services at Molten Technologies.

Stateless desktops are non-persistent, meaning that they get destroyed every time the user logs off, and reinstantiated for the next session. IT administrators can give their users the best of both worlds by using products to store a user customisation layer, containing all of the changes that the user has made to the desktop.

This means that a shared desktop image can be stored for the user, separately to the far thinner customisation data layer. The result: far less data to replicate, leading to a reduction in SAN or local storage costs.

Pooling costs

The alternative for the strong of heart is simply to offload the whole sorry mess onto someone else. "If you have an external virtual hosted desktop provider, you only need the almost universally accessible internet to get to your desktop," says Raynsford. "This can be a plus point for building disasters, such as an office flood, or if nobody can get there because of snow." External providers can also pool disaster recovery and share the costs across customers, he points out.

The same is true of application virtualisation systems such as Microsoft's App-V. It streams code to the local client, which then enables users to continue operating in the event of a network outage.

The danger with third party hosts, of course, is that they may not provide IT administrators with the level of configurability that they require. You'll need to assess how flexible the administrative interface is.

IT teams must also look into pricing mechanisms to see how the costs of software licenses vs rented operating systems and applications would stack up . It’s also worth keeping in mind what the licenses allow you to do. In the world of Windows for instance there are special licensing requirements for accessing Windows running on a server.

Don't underestimate the cost of making a virtualised desktop infrastructure truly resilient, then, but don't underestimate the things that you can do to help mitigate the tasks involved.

By Robin Birtstone

Read Original Story Here

 
Google threatens Chrome address bar with death PDF Print E-mail
Written by Urszula   
Wednesday, 02 March 2011 10:23

'Major' UI experiment vanishes urls

Google is exploring several "major" changes to the Chrome user interface, including a particularly compact user interface that actually hides the URL address bar when pages aren't loading.

In a recent post to the Chromium developer mailing list entitled "Major UI efforts", Google man Jeff Chang pointed to a public page describing four "window UI variants" for the Chromium OS project.

The first – known as "classic navigation" – is similar to the existing Chrome UI, but as Conceivably Tech observes, another layout receiving serious consideration – "compact navigation" – would be a significant departure from the browser as we know it.

Chromium is the open source incarnation of the Chrome browser, while Chromium OS serves as the basis for the upcoming Chrome OS operating system. Though the UI variants are intended for Chromium OS, Chang is writing on a Chromium mailing list and seems to indicate they'll be a part of Chromium as well. In any event, the two projects are meant to dovetail.

Currently, Chrome's URL address bar is always visible, alongside the navigation and menu buttons and just below your row of tabs. With the new "compact" design, navigation buttons are moved up alongside the tabs, and the address bar is only visible when a webpage is loading – though you can bring it back by clicking on the page's tab.

"If we take the address bar out of the tab, it can be used as both a launcher and switcher; the user doesn't have to worry about replacing their active tab," Google says. The UI looks something like this:

Chrome 'compact' UI experiment

Chrome "compact" UI

The interface re-separates the search and address bars – the two are combined in Chrome's current Omnibox setup. With "compact navigation," the search box is moved up alongside the tabs and the navigation buttons. "Search can be used as launcher and switcher," Google says. But it appears that the search box will still be used for direct navigation – i.e., visiting a page by directly typing a URL. The UI simply hides the url itself after a page loads.

The setup saves vertical real estate, Google says, but the company also points out several weaknesses. You, well, can't always see the current URL. Navigation controls and menus are not located within the individual tab and "lose context sensitivity". And the tab strip gets "crowded".

Google's "classic navigation" option is far more familiar. "The most basic navigation style is that of a single maximized Chromium window. This is the equivalent of the Chromium browser windowing UI in maximized mode." It looks like this:

Chrome classic UI experiment

Chrome "classic" UI

Google says that it's "focused" on these the classic and compact UI experiments, but two others are on the back burner. A "sidebar navigation" option puts the navigation buttons and address bar on the left-hand side of the browser. "By moving the tab-strip to the side, we gain a huge amount of real estate for tabs. The vertical alignment also allows for date ordering and grouping of tabs. By moving the address bar out of the tab and above the strip, it can be used both for navigation as well as search":

Chrome sidebtab UI experiment

Chrome "sidetab" UI

The company is also looking at a UI designed specifically for touchscreen devices. "For touch screens, we provide much larger tab and toolbar targets than on standard Chrome. This UI takes up more screen space, but is ideal for portrait devices, and can be autohidden to have full-screen content," Google says. "This treatment could be used on any edge of the screen, and it may be preferable to use the bottom edge depending on the device":

Chrome touchscreen UI experiment

Chrome "touchscreen" UI

Google is also developing a means of allowing users to set up multiple Chrome profiles across separate Chrome windows, and these can be mapped to separate online Google accounts. "Allowing different windows to run as different Chrome identities means that a user can have different open windows associated with different Google accounts, and correspondingly different sets of preferences, apps, bookmarks, and so on – all those elements which are bound to a specific user's identity," the company says. "Having multiple profiles in the Chrome browser also makes it easy to browse with separate identities without having to log in as separate users at the operating system level."

This may include actually using a tag on the browser itself to identify the Google account currently in use:

Chrome multiple profile UI

Google's Jeff Chang indicated that the company has already "begun work on getting the profile selection widget to show up on the browser window frame." And he says that Google is working to allow users to associate separate browser preferences with separate Google accounts.

Currently, Google lets you synchonize your Chrome and Google account preference across multiple machines – an important part of its Chrome OS play. The new multiple profile will still allow for this sort of synchronization. "In the multiple profiles model, the idea of syncing will need to adapt to the understanding that several distinct users (or, at least, identities) can be associated with a single browser instance," Google says. ®

Update: This story has been updated to add additional information about the distinction between Chromium and Chromium OS.

By Cade Metz

Read Original Story Here

 
Dual flash and disk desktops PDF Print E-mail
Written by Urszula   
Tuesday, 11 January 2011 13:17

Desktop users want faster boot and app load times just as much as notebook users and dual flash and hard disk drive systems could provide both.

Intel and Lenovo announced ThinkPad notebooks at CES last week, featuring both solid state drives (SSD) and hard drives (HDD) with 40GB or 80GB of Intel 310 flash used for storing the BIOS, operating system boot and application load, and a 2.5-inch HDD used for bulk data storage. A 9.7 second boot time was demo'd.

Read more...
 
<< Start < Prev 1 2 3 Next > End >>

Page 1 of 3

User Login

Search Articles

Take a Poll

Which Web Browser do you prefer?