News | Mail Archive | OS Software Downloads Ad Info ::
Subject: Databases | Java | Linux | Open Source | XML | Data | Tech

 Remember me

 Become a Member!
 Login Problems?

Recently Updated Mail Archives
NameLast Updated
Popular Mail Lists: Daily Proxies VPN OpenStack Hadoop nginx modpagespeed Android windows linux solaris osx ubuntu fedora enterprise crm ruby python java xml perl php cvs subversion version contol db
database mysql postgresql mobile telephony voip apple apache
sitemap (mail)

Posted Oct 29, 2004

Breaking the Network Barrier / KDE: From the Source

by George Staikos

Dazzle your friends and family, but more importantly, make your applications rock, by using KDE's fully networked desktop protocol handlers!

KDE is, by design, a fully networked desktop. Network files are accessible as readily and easily as local files from most applications. This is accomplished through special protocol handlers built into KDE, known as I/O slaves. These handlers implement a specific network protocol such as HTTP, FTP, or IMAP, and transparently interact with applications when they try to open a URL that requires that protocol.

In the KDE Info Center you will find a category called Protocols. If you select this category, you will be presented with a list of all the protocol handlers installed, and selecting a given handler will display some usage help (where available) in a panel to the right. A typical KDE installation supports approximately 75 different protocols! This can certainly be overwhelming, and very few users make use of more than a few of these. In fact, many of these protocol handlers are designed primarily for internal use by various applications, or as compression filters for other protocol handlers.

A complete list of installed protocol handlers can be found in the KDE Info Center. You can run this by opening the K-Menu, and running "Info Center" in the "System" sub-menu, or simply "Alt-F2" and run "kinfocenter".

The easiest way to explore and experiment with the different protocol handlers is to try them in Konqueror, the universal browser application. Not all protocols actually go out onto the network. For instance, if you type "fonts:/" into the Konqueror "Location:" prompt, you will get a virtual directory of folders with the fonts installed on the system. Incredibly, you can drag these fonts out of the folders to copy them, move them to the trash to uninstall them, or even drag new fonts into the folders to have them installed and made available to applications! You can even see iconic previews of the fonts as you browse, making it easy to see which font is the one you are looking for.

Some other interesting "local" protocol handlers include:
"audiocd:/" - A powerful tool to browse and play tracks on audio CDs. Includes transparent encoding into MP3 and OGG when dragging tracks off the CD.
"devices:/" - Presents a list of storage devices on the system, allowing browsing, mounting, unmounting, and other sorts of device manipulation.
"info:/" - Provides a very clean, easy-to-use interface to GNU info pages.
"man:/" - Provides access to the entire system manual.
"perldoc:/" - Provides access to the PERL manual, for PERL programmers.
"settings:/" - A mechanism to configure your KDE desktop from any place that accepts URLs.
"trash:/" - In KDE 3.4, will provide direct access to your trash bin.
"tar:/path/filename" and "zip:/path/filename" - Browse into TAR and ZIP files without unpacking them, opening a command prompt, or opening a packaging application. You can even edit the archive as though it were unpackaged!

Perhaps more interesting than the local protocol handlers are the network ones. They bring the network to the local desktop in a transparent way, making communication and collaboration downright trivial. You're probably already familiar with the HTTP protocol, used by websites to transfer web pages to the browser. KDE supports this protocol along with many others. For instance, you can browse FTP sites with the ftp:// protocol, or connect to the Microsoft Windows "network neighborhood" with the smb:/ protocol. Protocols with an equivalent protocol ending in the letter "s" generally signify that they support SSL encryption, such as "https", "ldaps", and "imaps".

Some interesting network protocol handlers include:
"ftp://host/" - A fully functional FTP client.
"http://host/" - A fully functional web client.
"imap://host/" - Access your IMAP mail account.
"ldap://host/" - LDAP directory browser.
"nntp://host/" - Access a Usenet news server.
"pop3://host/" - Access your POP3 mail account.
"sftp://host/" - SSH encrypted FTP.
"webdav://host/" - Webdav (AKA Webfolder) client for KDE.

Being able to do all of these things from a web browser is definitely a nice parlor trick, but in reality it's not a very easy way to use a computer. The real power of these protocol handlers is unleashed when they're used within various KDE applications. Any of these protocols can be used from the KDE file dialog, allowing files to be opened from or saved to any protocol! You can open your word processor, select File->Open, browse to a file on an FTP server, edit it, and save it back to the server all without leaving the word processor.

Finally, KDE includes one special protocol that lets you access another computer that isn't running traditional network services such as FTP and HTTP. This protocol is called "fish", and requires a running SSH server and PERL installed on the remote machine. Simply use the URL fish://host/ and log into the server when prompted. You can browse around the server, manipulate files with drag and drop, and edit files as though they were local. Many KDE users eventually find this to be an indispensable tool for accessing their files on other computers.

The integrated networking layer is certainly one of the strongest points of innovation in KDE. Microsoft Windows and Mac OS X have a long way to go to catch up with the robust, transparent functionality that KDE has provided since version 2.0.

George is a software developer from Toronto, Canada. He has been actively involved with the KDE project for over 5 years, developing KDE code and attending conferences to discuss and promote KDE and Linux on the desktop. He is presently the North American press contact for KDE, and is still an active developer. George has contributed to many different areas of KDE including the libraries and I/O subsystem, Konqueror, KMail, and various other applications.

blog comments powered by Disqus


Re: Breaking the Network Barrier / KDE: From the Source (Score: 0)
by Anonymous on Oct 29, 2004 - 09:34 AM
This article is a real eye opener. I have grazed the surface of I/O slaves with the FTP functionality (using it with kate for simple webdevel is pretty smooth), but the fish protocal, or news or anything. It's pretty darn cool. Great article.


Re: Breaking the Network Barrier / KDE: From the Source (Score: 0)
by Anonymous on Oct 29, 2004 - 01:50 PM
While the 'location independance' (being on the network or locally) is nice where it works, it isn't pervasive in KDE: I think that KNode is not able to work correctly on disconnected operation for example..

Re: Breaking the Network Barrier / KDE: From the Source (Score: 0)
by Anonymous on Oct 29, 2004 - 01:50 PM
The best protocol of them all "man:"

Just love it.


Re: Breaking the Network Barrier / KDE: From the Source (Score: 3, Interesting)
by Anonymous on Oct 29, 2004 - 02:28 PM
the real accomplishment will be the ability to have these protocols mounted so that NON-kde apps can access these resources. mplayer cannot use the smb:// i/o so you cannot play video files on a remote samba share using this method.

if kde would be smart enough to allow you to mount the location represented with the open-with command that would be great.

smb:/host/video/clip1.mpeg would translate to /smb/host/video/clip1.mpeg and kde would automagically mount it as such until nothing has accessed for a timeout. then, when navigating @ smb://host/video and you open-with mplayer, kde sends mplayer the local mount path and opens it!

THAT would be cool.

Re: Breaking the Network Barrier / KDE: From the Source (Score: 0)
by Anonymous on Oct 29, 2004 - 05:58 PM
Are these protocols accessible from javascript served from a remote web page? Like XMLHTTP functionality? It could be useful for stealing password files.

audiocd:/ (Score: 0)
by Anonymous on Oct 29, 2004 - 10:45 PM
I wrote a short guide to using the audiocd:/ slave some time ago.
You can read it here:

Re: Breaking the Network Barrier / KDE: From the Source (Score: 0)
by Anonymous on Oct 30, 2004 - 10:17 AM

Was wondering about the SMB:// IO-Slave?  There was no mention of it, and i believe for Linux in ther enterprise we need a Linux box to co-esist and participate easily in a Windows or Samba network,  does the smb:// io-slave have read/write access now?  and can we have do something about Lisa please, infact im wrong, lisa is not the problem but lan:// is, its not user friendly to start with.

thank you, just wanna see kde continue to be the best DE out there!

Re: Breaking the Network Barrier / KDE: From the Source (Score: 0)
by Anonymous on Oct 30, 2004 - 09:07 PM
My question is how to get a protocol that isn't listed as registered? Does one have to update all of KDE each time a new one is available?

Advertise With Us! | Comments are property of their posters.
Copyrighted (c) 2000-2016 SuperComfy, but we're happy to let you use what you wish with attribution.
All logos and trademarks are the property of their respective owners.
. Contact | Privacy Policy | Terms of Service

Page created in 0.260589 seconds.