5 Commits

Author	SHA1	Message	Date
Jelmer Vernooij	7ba2554d88	r18802: Use the pidl-generated code for the srvsvc interface, both client and server code. ... This has had some basic testing. I'll do more during the next couple of days and hopefully also make RPC-SRVSVC from Samba4 pass against it. (This used to be commit ef10672399)	2007-10-10 12:00:59 -05:00
Jelmer Vernooij	e5db7fee0f	r18572: Use the autogenerated client and server for the echo interface and implement ... some of the missing functions. RPC-ECHO now passes against Samba3. (This used to be commit 9e9a053661)	2007-10-10 11:51:51 -05:00
Volker Lendecke	430fa0eba0	r17348: Some C++ warnings ... (This used to be commit ae6b9b34e5)	2007-10-10 11:38:27 -05:00
Jeremy Allison	acf9d61421	r4088: Get medieval on our ass about malloc.... :-). Take control of all our allocation ... functions so we can funnel through some well known functions. Should help greatly with malloc checking. HEAD patch to follow. Jeremy. (This used to be commit 620f2e608f)	2007-10-10 10:53:32 -05:00
Tim Potter	065561932c	A new RPC pipe! The \pipe\echo named pipe is for testing large RPC ... requests and responses and is only compiled in when --enable-developer is passed to configure. It includes server and client side code for generating and responding to functions on this pipe. The functions are: - AddOne: add one to the uint32 argument and return ig - EchoData: echo back a variable sized char array to the caller - SourceData: request a variable sized char array - SinkData: send a variable sized char array and throw it away There's a win32 implementation of the client and server in the junkcode CVS repository in the rpcecho-win32 subdirectory. (This used to be commit 4ccd34ef83)	2003-04-11 04:09:14 +00:00