PATCH: KProtocolInfo's use of KProtocolManager::slaveProtocol

[Dawit A.]

Hello,

The following patch makes it an explicit requirement for a protocol
to declare that its support for proxying relies on another protocol.
This way the majority of protocols that do not support proxying get 
penalized when any of the static KProtocolInfo:: functions are 
invoked. 

This is specially true if you use automatic proxy detection, but do not 
have it setup. There is a noticable delay that can be preceived as 
a system "freeze-up".

-- 
Regards,
Dawit A.
"Preach what you practice, practice what you preach"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ftp.protocol.diff
Type: text/x-diff
Size: 490 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20040718/d8479035/attachment.diff>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kprotocolinfo.diff
Type: text/x-diff
Size: 5258 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20040718/d8479035/attachment-0001.diff>