PATCH samba cache and read-ahead

Jelmer Vernooij jelmer at samba.org
Fri Jan 11 15:47:45 GMT 2008


Am Freitag, den 11.01.2008, 15:41 +0000 schrieb Amin Azez:
> * Jelmer Vernooij wrote, On 11/01/08 15:31:
> > There is an explanation in prog_guide.txt in the root of the Samba 4 git
> > tree. 
> >
> > Examples of binding strings could be : ncalrpc:,
> > ncacn_ip_tcp:192.168.4.8 or ncacn_np:SOMEHOST.
> >   
> 
> What it is to read something missing out the bits I don't need, and then
> not reading it again cos I already read it!
> 
> I guess I want to use ncacn_np, then, I suppose:
> 
>   ncacn_np:remote-server.domain[\pipe\proxy]
The [\pipe\proxy] bit is optional. If it is not specified, it will be
  provided by the server through the end point mapper interface
 (basically a UUID -> endpoint address lookup).

> will be the binding I use. It seems like GUID's are not part of the
> binding? It seems to make the GUID redundant given that I specify the
> pipe name. (Or do I?)
The interface UUID is retrieved from the ndr_table_ pointer you specify
when connecting.

> Can the remote server make rpc calls over the same connection?
The connection is really client<->server. Only the client can make
requests, the server can only answer.

> Can the client register callbacks over the RPC, which the remote server
> can issue periodically?
You can open back a connection from the server to the client, but I'm
not sure if we would want to go there :-) Why would you need
notifications?

Cheers,

Jelmer
-- 
Jelmer Vernooij <jelmer at samba.org> - http://samba.org/~jelmer/
Jabber: jelmer at jabber.fsfe.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 307 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.samba.org/archive/samba-technical/attachments/20080111/668bcacd/attachment.bin


More information about the samba-technical mailing list