Sequenced rpc pipes
abartlet at samba.org
Tue Nov 1 22:00:43 GMT 2005
On Tue, 2005-11-01 at 21:36 +0100, Volker Lendecke wrote:
> On Tue, Nov 01, 2005 at 12:09:08AM +0100, Jelmer Vernooij wrote:
> > Yes, that's the default. There is a [async] attribute in IDL that can
> > make a specific call asynchronous (support for >= W2K). More
> > information is at
> > http://msdn.microsoft.com/library/en-us/rpc/rpc/asynchronous_rpc.asp
> Attached find an attempt to implement it. The pidl part is Jelmer's work
> (thanks for the very quick reaction!). I'm not sure the semantics are correct
> if the pipe has both sync and async operations
The easy way to ensure we understand the semantics would be to extend
the echo test, to mix some sync and async operations.
My gut feeling is that a sync operation should leave a flag on the pipe
'sync_busy', which should prevent sending other packets, which can be
removed on the receipt of a reply. We (if running signed/sealed) should
also check gensec_have_feature(gensec, GENSEC_FEATURE_ASYNC_REPLIES).
> , but for the torture async
> lookupsids tests it works as expected. If you apply the [async] flag to
> LookupSids in lsa.idl, you see the requests fly and the responses come in
> later, if you keep it as it is, you see client and server play ping-pong.
> What do you think?
Was that just against Samba4, or is LookupSids async against Win2k3?
Andrew Bartlett http://samba.org/~abartlet/
Samba Developer, SuSE Labs, Novell Inc. http://suse.de
Authentication Developer, Samba Team http://samba.org
Student Network Administrator, Hawker College http://hawkerc.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.samba.org/archive/samba-technical/attachments/20051102/163118c1/attachment.bin
More information about the samba-technical