Article View: alt.pl.comp.lang.csharp
Article #563Re: RPC (Remote Procedure Call) w .NET
From: Marcin Hoppe
Date: Wed, 10 Mar 2004 13:58
Date: Wed, 10 Mar 2004 13:58
15 lines
1576 bytes
1576 bytes
Bartek Szafraniec wrote: > Mam pytanie czy istnieje możliwość zaprogramowania > mechanizmu RPC na platformie .NET? > Orginalnie mechanizm ten wymyślono dla Uniksów i podobno tylko > tam jest on poprawnie zaimplementowany i wspomagany przez > system operacyjny. Czy to prawda? > Jesli mozecie to poprosze o jakies przykłady w C++ lub C#. Hmm. A Web Services? -- Marcin Hoppe E-mail: marcin...@gazeta.pl WWW: http://marcinhoppe.republika.pl Gadu Gadu: 2222891
Technical Details
Message-ID:
<c2n6ud$efi$1@inews.gazeta.pl>Path:
mbox-mo1.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-xit-08!supernews.com!priapus.visi.com!orange.octanews.net!news-out.visi.com!petbe.visi.com!news.octanews.net!newsfeed.tpinternet.pl!newsfeed.gazeta.pl!news.gazeta.pl!not-for-mailReferences:
<c2n64o$t3n$1@opal.futuro.pl>Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-xit-08!supernews.com!priapus.visi.com!orange.octanews.net!news-out.visi.com!petbe.visi.com!news.octanews.net!newsfeed.tpinternet.pl!newsfeed.gazeta.pl!news.gazeta.pl!not-for-mail From: Marcin Hoppe <marcin.hop...@gazeta.pl> Newsgroups: alt.pl.comp.lang.csharp Subject: Re: RPC (Remote Procedure Call) w .NET Date: Wed, 10 Mar 2004 14:58:36 +0100 Organization: Portal Gazeta.pl -> http://www.gazeta.pl Lines: 15 Message-ID: <c2n6ud$efi$1@inews.gazeta.pl> References: <c2n64o$t3n$1@opal.futuro.pl> Reply-To: marcin.hop...@gazeta.pl NNTP-Posting-Host: ws85.neoplus.adsl.tpnet.pl Mime-Version: 1.0 X-Trace: inews.gazeta.pl 1078927118 14834 80.54.56.85 (10 Mar 2004 13:58:38 GMT) X-Complaints-To: use...@agora.pl NNTP-Posting-Date: Wed, 10 Mar 2004 13:58:38 +0000 (UTC) X-Accept-Language: en-us, en X-User: marcin.hoppe User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) In-Reply-To: <c2n64o$t3n$1@opal.futuro.pl> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit