comp.lang.idl-pvwave archive: archive » Re: How to organize client-server IDL application?

Home » Public Forums » archive » Re: How to organize client-server IDL application?

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: How to organize client-server IDL application? [message #26123 is a reply to message #26055]

Thu, 02 August 2001 20:21

alt
Messages: 28
Registered: August 2001

Junior Member

Stein Vidar Hagfors Haugan <shaugan@esa.nascom.nasa.gov> wrote in message news:<xmz3d7dnlod.fsf@esa.nascom.nasa.gov>...
> JD Smith <jdsmith@astro.cornell.edu> writes:
>
>> Altyntsev Dmitriy wrote:
>>>
>>> Hi,
>>>
>>> I need to build classic client-server IDL application. I have some
>>
> Or write a DLM on the client side that uses RPC calls to communicate with
> the server.
>
> --
> ------------------------------------------------------------ --------------
> Stein Vidar Hagfors Haugan
> ESA SOHO SOC/European Space Agency Science Operations Coordinator for SOHO
>
> NASA Goddard Space Flight Center, Email: shaugan@esa.nascom.nasa.gov
> Mail Code 682.3, Bld. 26, Room G-1, Tel.: 1-301-286-9028/240-354-6066
> Greenbelt, Maryland 20771, USA. Fax: 1-301-286-0264
> ------------------------------------------------------------ --------------

Thank you. I think it would be the easiest way to solve this problem.

Dmitriy

Report message to a moderator

[Message index]

		Re: How to organize client-server IDL application? By: HILBERMAN on Wed, 01 August 2001 11:39
		Re: How to organize client-server IDL application? By: Stein Vidar Hagfors H[1] on Tue, 31 July 2001 08:49
		Re: How to organize client-server IDL application? By: John-David T. Smith on Tue, 31 July 2001 08:36
		Re: How to organize client-server IDL application? By: alt on Thu, 02 August 2001 20:21

Previous Topic:	Re: Using C++ DLM's With IDL?
Next Topic:	Re: Print format question for the Experts

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Oct 11 09:23:19 PDT 2025

Total time taken to generate the page: 1.04110 seconds