From: SMTP%"everhart@mail09.mitre.org" 19-DEC-1997 20:20:52.94 To: everhart@gce.com (everhart@gce.com) CC: Subj: FWD: Re: NTDOM: DCE/RPC over SMB Trans Return-Path: everhart@mail09.mitre.org Received: by arisia.gce.com (UCX V4.1-12C, OpenVMS V7.1 VAX); Fri, 19 Dec 1997 20:20:38 -0500 Received: from mbunix.mitre.org (mbunix.mitre.org [129.83.20.100]) by mercury.mv.net (8.8.8/mem-971025) with ESMTP id PAA18255 for ; Fri, 19 Dec 1997 15:42:00 -0500 (EST) Received: from TGATE3 (tgate3.mitre.org [129.83.20.27]) by mbunix.mitre.org (8.8.8/8.8.8/mitre.0) with ESMTP id PAA17083 for ; Fri, 19 Dec 1997 15:40:31 -0500 (EST) Received: from mail09.mitre.org (unverified [129.83.20.43]) by tgate3.mitre.org (EMWAC SMTPRS 0.83) with SMTP id ; Fri, 19 Dec 1997 15:38:43 -0500 Received: by mail09.mitre.org; (5.65v3.2/1.1.8.2/22Jun94-0628PM) id AA14259; Fri, 19 Dec 1997 15:38:43 -0500 Subject: FWD: Re: NTDOM: DCE/RPC over SMB Trans From: everhart@mail09.mitre.org (Glenn C. Everhart) To: everhart@gce.com (everhart@gce.com) Message-Id: <971219153842.20718@mail09.mitre.org.0> Date: Fri, 19 Dec 97 15:38:42 -0500 X-Mailer: MailWorks 2.0-4 Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===_tgate3_68749_93800407_===" --===_tgate3_68749_93800407_=== Content-Type: text/plain; charset="us-ascii" free dce sources reference. ----- Forwarded message follows ----- X-Priority: 3 X-Msmail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 Date: Fri, 19 Dec 97 15:28:55 -0500 Reply-To: Common Internet File System From: Seiichi Tatsukawa Subject: Re: NTDOM: DCE/RPC over SMB Trans To: -----Original Message----- From: Luke Kenneth Casson Leighton :the code i have written up, so far, has been released under the GPL. :barring wars or flash floods of frogs, it will remain so. I have done hand-marshalling/unmarshalling of the NDR encoded data streams in the past. For simple data structures, it's not too difficult. But, once you encounter complicated ones, like a nested conformant/varying arrays, embedded pointers, pipes (well, Microsoft doesn't probably use pipes because their original DCE/RPC implementation lacked it), etc., things become tough. If they use client context handles, you need more than NDR encoder/decoder. And whenever Microsoft changes the IDL definitions, you'll have to re-write your codes as opposed to running the IDL compiler. You may want to check the free DCE 1.2.2 sources available from The Open Group (http://www.camb.opengroup.org/dce/download/) which includes DCE/RPC IDL compiler and NDR marshalling/unmarshalling engine. The licensing term may not fit you and you'll need to get rid of all pthread calls, but it is a real thing and interoperates with MS/RPC. (Microsoft ran OSF (now Open Group)'s DCE/RPC validation suite against MS/RPC.) You don't probably need DCE/RPC runtime, just IDL and its runtime library which are easier to port. And, as Nat said, if someone actually gave you the IDL files, you are all set. :-) --- Seiichi + Seiichi Tatsukawa + + Rational Software, Lexington, MA + ---------------------------------------------------------------- Users Guide http://www.microsoft.com/sitebuilder/resource/mailfaq.asp contains important info including how to unsubscribe. Save time, search the archives at http://discuss.microsoft.com/archives/index.html ----- End of forwarded message ----- --===_tgate3_68749_93800407_===--