sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-02-02 09:47:23 +03:00
Code

r6226: A couple of small typos ...

Browse Source 
(This used to be commit d2c5320a18821439e49d3f7bffebc47129b8b057)
This commit is contained in:
Richard Sharpe 2005-04-06 16:48:28 +00:00 committed by Gerald (Jerry) Carter
parent 7c6c366150
commit 6d0c1be1a4
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
prog_guide.txt
View File

@ -207,7 +207,7 @@ an idea of what I am talking about.
In Samba3 many of the core wire structures in the SMB protocol were
never explicitly defined in Samba. Instead, our parse and generation
functions just worked directly with wire buffers. The biggest problem
with this is that is tied our parse code with out "business logic"
with this is that is tied our parse code with our "business logic"
much too closely, which meant the code got extremely confusing to
read.
@ -395,7 +395,7 @@ function, so smbd has a _send() function and the parse function for
each SMB.
As an example go and have a look at reply_getatr_send() and
reply_getatr() in smbd/reply.c. Read them? Good.
reply_getatr() in smb_server/reply.c. Read them? Good.
Notice that reply_getatr() sets up the req->async structure to contain
the send function. Thats how the backend gets to do an async reply, it