<div>OK. I was thinking why should named pipe concern itself with how a blob has arrived i.e.</div>
<div>either via smbtrans or via smbwrite?</div>
<div>For example, in case of QNmPipeInfo, if the blob can contain necessary info such as</div>
<div>function name (0x26) and Infolevel (0x1), named pipe should have a response ready</div>
<div>to be read.<br><br></div>
<div class="gmail_quote">On Thu, Sep 24, 2009 at 12:57 AM, Volker Lendecke <span dir="ltr"><<a href="mailto:Volker.Lendecke@sernet.de">Volker.Lendecke@sernet.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div></div>
<div class="h5">On Wed, Sep 23, 2009 at 02:20:49PM -0500, Shirish Pargaonkar wrote:<br>> In Samba, can a QNmPipeInfo functionality be implemented using SMB Write and<br>> SMB Read<br>> instead of SMB Trans with command QNmPipeInfo?<br>
><br>> I can send DCE RPC bind using SMB Write and read the bind ack using SMB Read<br>> instead<br>> of SMB Trans TransactNmPipe.<br>> I was wondering if similar could be done to implement various named pipe<br>
> functions such as<br>> SetNmPHandState, QNmPHandState, and WaitNamedPipe by sending an appropriate<br>> blob.<br><br></div></div>Hmmm. Not that I know of. Those transfer extra metadata that<br>is not really inline.<br>
<font color="#888888"><br>Volker<br></font><br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v1.4.9 (GNU/Linux)<br><br>iEYEARECAAYFAkq7CkoACgkQbsgDfmnSbrYnrQCeONWrEuPzIJeEjs9ApMnM9OMP<br>zhAAoJPwHljiDgkHDb6ZZpfOrAvpJwjK<br>
=1nmb<br>-----END PGP SIGNATURE-----<br><br></blockquote></div><br>