From: James S. <jam...@op...> - 2007-05-31 02:13:21
|
Hi Folks, I hope some of you have had some Microsnot experience writing client RPC applications to talk to a *nix style RPC server. I've just read http://docs.freebsd.org/44doc/psd/22.rpcgen/paper.pdf that describes how to write both a simple server and client application compiled and run on *nix. With little effort I got it working between 2 Linux boxes. My goal is to have a Linux RPC server application that is remotely called by a WinXP client. Trouble is, when I started reading the Windows documentation it left me in a daze. I started from here http://msdn2.microsoft.com/en-us/library/aa379010.aspx and when I got to here http://msdn2.microsoft.com/en-us/library/aa378705.aspx I was nearly ready to beg for mercy ;-) I found a (not) working example http://www.codeproject.com/internet/rpcintro1.asp . When I go to compile the midl generated Example1_c.c file with gcc I get all sorts of warnings and errors. Does anyone know of or have a decent MinGW RPC working example I could learn from? Cheers, James. |
From: James S. <jam...@op...> - 2007-05-31 02:54:09
|
On Thu, 2007-05-31 at 12:13 +1000, James Steward wrote: > I found a (not) working example > http://www.codeproject.com/internet/rpcintro1.asp . When I go to > compile the midl generated Example1_c.c file with gcc I get all sorts of > warnings and errors. In trying to compile just the Example1_c.c file, I used the command, gcc -c -DTARGET_IS_NT50_OR_LATER=1 -o Example1_c.o Example1_c.c Without the -DTARGET.... the compile complains and errors out. The /mingw/include/rpcdcep.h file structure definition for RPC_CLIENT_INTERFACE differs from the one I found in c:\Program Files\Microsoft Platform SDK\Include\RpcDcep.h. There is a missing unsigned int Flags at the end of the structure in the MinGW version. Regards, James. |
From: chafar <ch...@ch...> - 2007-05-31 06:20:32
|
James Steward escribió: > Hi Folks, > > I hope some of you have had some Microsnot experience writing client RPC > applications to talk to a *nix style RPC server. > > I've just read http://docs.freebsd.org/44doc/psd/22.rpcgen/paper.pdf > that describes how to write both a simple server and client application > compiled and run on *nix. With little effort I got it working between 2 > Linux boxes. > Apart from your compiling troubles, you may want to know about DCE-RPC / NDR and ONC-RPC / XDR. cheers -- chafar |
From: James S. <jam...@op...> - 2007-06-01 00:27:27
|
On Thu, 2007-05-31 at 08:20 +0200, chafar wrote: > James Steward escribió: > > Hi Folks, > > > > I hope some of you have had some Microsnot experience writing client RPC > > applications to talk to a *nix style RPC server. > > > > I've just read http://docs.freebsd.org/44doc/psd/22.rpcgen/paper.pdf > > that describes how to write both a simple server and client application > > compiled and run on *nix. With little effort I got it working between 2 > > Linux boxes. > > > > Apart from your compiling troubles, you may want to know about DCE-RPC / > NDR and ONC-RPC / XDR. Yes, thank you. And what about SOAP, CORBA, MSRPC, XML-RPC, etc, etc. At this stage I'm thinking it might be quicker to roll my own! It doesn't need to be hellishly complex. If ONC-RPC just worked at both ends it would be worth while, but it doesn't seem to be that easy. (And yes, I've written protocols before, so I have an idea of what I'm in for ;-) Regards, James. |
From: Dongsheng S. <don...@gm...> - 2007-06-01 06:00:13
|
VGhlIGZyZWUgT05DLVJQQyBmb3Igd2luZG93cyBxdWl0ZSBvbGQsIGJ1dCByZWFsbHkgc3RhYmxl LiBEQ0UtUlBDIGZvcgpsaW51eCBvdXQgb2YgZGF0ZSB0b28uIFNlZSBzYW1iYSBwcm9qZWN0IGZv ciBNU1JQQyB3aXRoaW4gdW5peC4KCkkgcHJlZmVyIHVzZSBYTUwtUlBDLCBDT1JCQSwgb3IgU09B UC4KCjIwMDcvNi8xLCBKYW1lcyBTdGV3YXJkIDxqYW1lc3N0ZXdhcmRAb3B0dXNuZXQuY29tLmF1 PjoKPiBPbiBUaHUsIDIwMDctMDUtMzEgYXQgMDg6MjAgKzAyMDAsIGNoYWZhciB3cm90ZToKPiA+ IEphbWVzIFN0ZXdhcmQgZXNjcmliacOzOgo+ID4gPiBIaSBGb2xrcywKPiA+ID4KPiA+ID4gSSBo b3BlIHNvbWUgb2YgeW91IGhhdmUgaGFkIHNvbWUgTWljcm9zbm90IGV4cGVyaWVuY2Ugd3JpdGlu ZyBjbGllbnQgUlBDCj4gPiA+IGFwcGxpY2F0aW9ucyB0byB0YWxrIHRvIGEgKm5peCBzdHlsZSBS UEMgc2VydmVyLgo+ID4gPgo+ID4gPiBJJ3ZlIGp1c3QgcmVhZCBodHRwOi8vZG9jcy5mcmVlYnNk Lm9yZy80NGRvYy9wc2QvMjIucnBjZ2VuL3BhcGVyLnBkZgo+ID4gPiB0aGF0IGRlc2NyaWJlcyBo b3cgdG8gd3JpdGUgYm90aCBhIHNpbXBsZSBzZXJ2ZXIgYW5kIGNsaWVudCBhcHBsaWNhdGlvbgo+ ID4gPiBjb21waWxlZCBhbmQgcnVuIG9uICpuaXguICBXaXRoIGxpdHRsZSBlZmZvcnQgSSBnb3Qg aXQgd29ya2luZyBiZXR3ZWVuIDIKPiA+ID4gTGludXggYm94ZXMuCj4gPiA+Cj4gPgo+ID4gQXBh cnQgZnJvbSB5b3VyIGNvbXBpbGluZyB0cm91YmxlcywgeW91IG1heSB3YW50IHRvIGtub3cgYWJv dXQgRENFLVJQQyAvCj4gPiAgIE5EUiBhbmQgT05DLVJQQyAvIFhEUi4KPgo+IFllcywgdGhhbmsg eW91LiAgQW5kIHdoYXQgYWJvdXQgU09BUCwgQ09SQkEsIE1TUlBDLCBYTUwtUlBDLCBldGMsIGV0 Yy4KPgo+IEF0IHRoaXMgc3RhZ2UgSSdtIHRoaW5raW5nIGl0IG1pZ2h0IGJlIHF1aWNrZXIgdG8g cm9sbCBteSBvd24hICBJdAo+IGRvZXNuJ3QgbmVlZCB0byBiZSBoZWxsaXNobHkgY29tcGxleC4g IElmIE9OQy1SUEMganVzdCB3b3JrZWQgYXQgYm90aAo+IGVuZHMgaXQgd291bGQgYmUgd29ydGgg d2hpbGUsIGJ1dCBpdCBkb2Vzbid0IHNlZW0gdG8gYmUgdGhhdCBlYXN5Lgo+Cj4gKEFuZCB5ZXMs IEkndmUgd3JpdHRlbiBwcm90b2NvbHMgYmVmb3JlLCBzbyBJIGhhdmUgYW4gaWRlYSBvZiB3aGF0 IEknbQo+IGluIGZvciA7LSkKPgo+IFJlZ2FyZHMsCj4gSmFtZXMuCj4KPgo+IC0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0KPiBUaGlzIFNGLm5ldCBlbWFpbCBpcyBzcG9uc29yZWQgYnkgREIyIEV4cHJlc3MKPiBE b3dubG9hZCBEQjIgRXhwcmVzcyBDIC0gdGhlIEZSRUUgdmVyc2lvbiBvZiBEQjIgZXhwcmVzcyBh bmQgdGFrZQo+IGNvbnRyb2wgb2YgeW91ciBYTUwuIE5vIGxpbWl0cy4gSnVzdCBkYXRhLiBDbGlj ayB0byBnZXQgaXQgbm93Lgo+IGh0dHA6Ly9zb3VyY2Vmb3JnZS5uZXQvcG93ZXJiYXIvZGIyLwo+ IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gTWluR1ct dXNlcnMgbWFpbGluZyBsaXN0Cj4gTWluR1ctdXNlcnNAbGlzdHMuc291cmNlZm9yZ2UubmV0Cj4K PiBZb3UgbWF5IGNoYW5nZSB5b3VyIE1pbkdXIEFjY291bnQgT3B0aW9ucyBvciB1bnN1YnNjcmli ZSBhdDoKPiBodHRwczovL2xpc3RzLnNvdXJjZWZvcmdlLm5ldC9saXN0cy9saXN0aW5mby9taW5n dy11c2Vycwo+Cg== |
From: Dongsheng S. <don...@gm...> - 2007-06-01 06:04:10
|
ONC/RPC for Windows NT/95: http://www.plt.rwth-aachen.de/index.php?id=258 for 2007/6/1, Dongsheng Song <don...@gm...>: > The free ONC-RPC for windows quite old, but really stable. DCE-RPC for > linux out of date too. See samba project for MSRPC within unix. > > I prefer use XML-RPC, CORBA, or SOAP. > |
From: Dongsheng S. <don...@gm...> - 2007-06-01 06:04:22
|
ONC/RPC for Windows NT/95: http://www.plt.rwth-aachen.de/index.php?id=258x 2007/6/1, Dongsheng Song <don...@gm...>: > The free ONC-RPC for windows quite old, but really stable. DCE-RPC for > linux out of date too. See samba project for MSRPC within unix. > > I prefer use XML-RPC, CORBA, or SOAP. > |
From: chafar <ch...@ch...> - 2007-06-01 07:42:29
|
James Steward escribió: > On Thu, 2007-05-31 at 08:20 +0200, chafar wrote: >> James Steward escribió: >>> Hi Folks, >>> >>> I hope some of you have had some Microsnot experience writing client RPC >>> applications to talk to a *nix style RPC server. >>> >>> I've just read http://docs.freebsd.org/44doc/psd/22.rpcgen/paper.pdf >>> that describes how to write both a simple server and client application >>> compiled and run on *nix. With little effort I got it working between 2 >>> Linux boxes. >>> >> Apart from your compiling troubles, you may want to know about DCE-RPC / >> NDR and ONC-RPC / XDR. > > Yes, thank you. And what about SOAP, CORBA, MSRPC, XML-RPC, etc, etc. > > At this stage I'm thinking it might be quicker to roll my own! It > doesn't need to be hellishly complex. If ONC-RPC just worked at both > ends it would be worth while, but it doesn't seem to be that easy. Yeap, sorry. But the fact that win implements DCE-RPC while linux ONC-RPC is not my fault. You didn't mention anything about it and I just wanted to call your attention about. > > (And yes, I've written protocols before, so I have an idea of what I'm > in for ;-) > I didn't made any assumption about whatever skills you may have, but if it could sound that way, my apologies. Regards. -- chafar |
From: James S. <jam...@op...> - 2007-06-01 21:02:45
|
On Fri, 2007-06-01 at 09:42 +0200, chafar wrote: > James Steward escribió: > > (And yes, I've written protocols before, so I have an idea of what I'm > > in for ;-) > I didn't made any assumption about whatever skills you may have, but if > it could sound that way, my apologies. No need. I was preempting those who would say I should stick to some well established protocol is all. Cheers, James. |