svn commit: samba r1578 - in branches/SAMBA_4_0/source: client include lib libcli/raw ntvfs/cifs smb_server torture torture/basic

[tridge at samba.org]

Author: tridge
Date: 2004-07-23 06:40:49 +0000 (Fri, 23 Jul 2004)
New Revision: 1578

Modified:
   branches/SAMBA_4_0/source/client/client.c
   branches/SAMBA_4_0/source/include/cli_context.h
   branches/SAMBA_4_0/source/include/dlinklist.h
   branches/SAMBA_4_0/source/include/events.h
   branches/SAMBA_4_0/source/include/rewrite.h
   branches/SAMBA_4_0/source/lib/events.c
   branches/SAMBA_4_0/source/libcli/raw/clisocket.c
   branches/SAMBA_4_0/source/libcli/raw/clitransport.c
   branches/SAMBA_4_0/source/libcli/raw/rawrequest.c
   branches/SAMBA_4_0/source/ntvfs/cifs/vfs_cifs.c
   branches/SAMBA_4_0/source/smb_server/smb_server.c
   branches/SAMBA_4_0/source/torture/basic/scanner.c
   branches/SAMBA_4_0/source/torture/gentest.c
Log:
the first stage of the async client rewrite.

Up to now the client code has had an async API, and operated
asynchronously at the packet level, but was not truly async in that it
assumed that it could always write to the socket and when a partial
packet came in that it could block waiting for the rest of the packet. 

This change makes the SMB client library full async, by adding a
separate outgoing packet queue, using non-blocking socket IO and
having a input buffer that can fill asynchonously until the full
packet has arrived.

The main complexity was in dealing with the events structure when
using the CIFS proxy backend. In that case the same events structure
needs to be used in both the client library and the main smbd server,
so that when the client library is waiting for a reply that the main
server keeps processing packets. This required some changes in the
events library code.

Next step is to make the generated rpc client code use these new
capabilities.


WebSVN: http://websvn.samba.org/websvn/changeset.php?rep=samba&path=/branches/SAMBA_4_0/source&rev=1578&nolog=1