| commit | 2882b5b5733c9aadb4a5312c92526c3224227733 | |
| author | Sam Liddicott <sam@liddicott.com> | |
| Fri, 7 Nov 2008 15:39:58 +0000 (7 15:39 +0000) | ||
| committer | Sam Liddicott <sam@liddicott.com> | |
| Wed, 10 Dec 2008 10:10:53 +0000 (10 10:10 +0000) | ||
| tree | 16aa065e0dc5cf2aecffc3f145c25f0dca3ca296 | treesnapshot (tar.gz zip) |
| parent | 264877bf8e26506f68fef3bea421ef38c05e5066 | commitdiff |
proxy rpc
After much discussion; The proxies will communicate with idl defined messages
and NDR encoding sent by ntioctl within the session.
There will therefore be an implicit fnum associated with the ntioctl which
identifies the file on which the proxy function is to operate.
I'm not entirely happy with that out-of-band-data so that may change to be IN
the NDR encoded data as well; but the tid and session is also out-of-band and
used to interpret the fnum anyway, so maybe we won't worry about that right now.
After much discussion; The proxies will communicate with idl defined messages
and NDR encoding sent by ntioctl within the session.
There will therefore be an implicit fnum associated with the ntioctl which
identifies the file on which the proxy function is to operate.
I'm not entirely happy with that out-of-band-data so that may change to be IN
the NDR encoded data as well; but the tid and session is also out-of-band and
used to interpret the fnum anyway, so maybe we won't worry about that right now.
| source4/librpc/config.mk | diffblobblamehistory | |
| source4/librpc/idl/proxy.idl | [new file with mode: 0644] | blob |
| source4/ntvfs/proxy/config.mk | diffblobblamehistory |