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

List:       kde-devel
Subject:    Re: kio_smb patch and questions
From:       Frank Schwanz <schwanz () fh-brandenburg ! de>
Date:       2001-12-05 0:51:14
[Download RAW message or body]

Am Mittwoch, 5. Dezember 2001 01:04 schrieb aleXXX:
> On Tue 04 Dec 01 22:33, Frank Schwanz wrote:
> > Am Montag, 3. Dezember 2001 22:36 schrieb aleXXX:
> > > On Mon 03 Dec 01 15:21, Frank Schwanz wrote:
> > > > Hello,
> > > >
> > > > regarding to the discussion about url_path a made a patch. It solves
> > > > the treeview problems and does follows for the different urls :
> > >
> > > ...
> > >
> > > > smb://host -> show the shares			= WORKS
> > > > smb://host					= WORKS (redirect smb://host/)
> > > > smb://group/ -> show the hosts			= WORKS
> > > > smb://group					= WORKS (redirect smb://group/)
> > >
> > > I would prefer avoiding these ambiguous URLs with smb://group . How do
> > > you find out whether group is a group and really no host ?
> >
> > Does libsmbclient. Or nmblookup name -S and look for <group>.
> >
> > > Does it also work reliable for urls like smb://blah/fasel/more/stuff ?
> >
> > What is blah and what is fasel ?
>
> Well, this is the question :-)
> I mean, you are able to find it out reliable ?
>
> > smb://group/host 	==> no, we should try to redirect to smb:/group/host/ ?
>
> I wouldn't support url's like smb://group/host, only smb://host
>
> I just found this :
>
> http://kt.linuxcare.com/samba/sm20010115_38.epl#1
thanks, it shows we are on the way.
>
> They discussed exactly the same syntax problem.
> And (I knew I was right) they state that the browse list stuff actually
> doesn't belong to smb (that's why I wrote my lan:/ stuff, since it is
> logically a separate functionality).
Smb is not only CIFS. Means browsing is included in smb protocol. A user 
don't know about the difference and won't know about it. lan:/ does more than 
smb:/ . The user accept it as a complete over view.
Problem is the smb:// it's not valid i think, but I would prefere it against 
smb:/ .

For complete uri I prefere  
smb://[[[domain;]user[:password]@]server[:port]][/share[/path[/file]]] .

smb:/group/host or smb://group/host should redirect to smb://group/host. But 
here we have the old problems in tree view. (the host will be deleted from 
tree if redirected)

> After reading their discussion, I'd still say that in smb://something
> "something" should *always* be a host.
> If you want to, you can redirect smb:// to smb:/ which shows the
> workgroups.
you mean  smb://workgroup will be redirected to smb:/workgroup ?


>
> If you want to we can also incorporate the browsing list functionality in
> my lisa ( lisa-home.sourceforge.net) server, so you enter lan:/ and see all
> workgroups, with the added benefit, that you are not only able to browse
> their smb shares, but also their ftp and http shares, ssh (fish) can be
> added without problem. And we wouldn't have ambiguous URLs.
how do you want resolve the problems with netbiosname and dns name ? lan:/ is 
good in a network with dnsnames. Here we have dnsnames stw001 ... stw250 and 
everyone has his own netbiosname/smbname. But it's no problem to include it.

frank
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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