[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Enhancing lan:/ and rlan:/
From:       Alexander Neundorf <neundorf () kde ! org>
Date:       2003-06-22 18:21:46
[Download RAW message or body]

On Saturday 21 June 2003 19:28, Jens Benecke wrote:
> Hello,
>
> I've discussed parts of the following suggestions in the BTS already.
> (http://bugs.kde.org/show_bug.cgi?id=58835) I would like lan:/ to bring
> more consistency into the KDE desktop, especially regarding display of
> remote hosts within KDE.
>
> In short, I would like three things to happen - and I'm perfectly
> willing to participate in making them happen. :-)
>
>
> - Make lan:/ more verbose, better for non-technical users ("what is this
>   SMB folder? I just want to copy a file from the other computer!")
>
>   A (fake) screenshot that shows what I thought about of is at
>   http://bugs.kde.org/attachment.cgi?id=1646&action=view
>
>   It doesn't have to look exactly like that, it's just an idea. :)
>
>
> - Everytime you manually connect to a host via a 'file-like' protocol
>   that lisa knows*, _add_ this host to the list of hosts displayed in
>   the lan:/ protocol. This solves three problems:

Good idea, but it has a problem: lisa scans (or gets the scanned list) 
according to /etc/lisarc. This one is systemwide. It can't be changed if one 
user visits another host.
So I would have to implement it in the kio_lan ioslave. The pinging isn't a 
good idea, since this would require root privileges for the ioslave.
Another way would be if a user visits fish://somehost, the lan-ioslave (damn, 
how should the information from the fish-ioslave get to the lan-ioslave ?) 
could remember the service (here: ssh) and then, if it is about to ask lisa 
for the hosts, also check the ssh-port if "somehost", i.e. no pinging.
This could work.

The one thing I don't know is how the information about visiting "somehost" 
via fish should get to the lan-ioslave. 

And, which hosts should be remembered ? fish, ftp ?

>   + one can let the host stay inside lan:/ for the session, then lisa does
> not need to be changed. If the host entry should be saved, the user must
> either use reslisa, or enter the root password to change lisarc, _or_
> change the lisa protocol, so that lisa can be told to scan new hosts at
> runtime (is that a good idea?).

No, since it is also possible that the lisa-daemon doesn't scan itself, but 
gets the information from a "master"-lisa daemon in the network, and all 
lisa-daemons in a network should ideally be configured the same way.

BTW, should I rename the binary from "lisa" to "lisad" ?

>     I would propse a lan:/ "subfolder" called (maybe) "Other computers",
>     which contains _temporary_ entries of all machines that were
>     accessed by the above mentioned procotols during the _current_
>     session. LISA doesn't need to know about them - we know the user
>     accessed a service and it was successful, so there is no need for
>     the host to be re-scanned.

Well, but we don't know whether the host is still up later on.


If somebody has an idea about the mentioned problem I'll have a look at it ... 
(but be patient)

Bye
Alex
-- 
Work: alexander.neundorf@jenoptik.com - http://www.jenoptik-los.de
Home: neundorf@kde.org                - http://www.kde.org
      alex@neundorf.net               - http://www.neundorf.net

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]