Having worked in COM & DCOM I would have to agree with 'pjones' that the
concept is pretty good, but the reality is that you get some nasty
problems (such as the NT user problem below). I have also found IP
sockets (actually using UDP) a better way to go, though I have not
looked at Corba yet.
Grant Black
Software Developer
SmartMove (NZ) Ltd
Phone: +64 9 361-0219 extn 719
Fax : +64 9 361-0211
Email: [EMAIL PROTECTED]
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 21, 1999 9:25 AM
> To: Multiple recipients of list delphi
> Subject: RE: [DUG]: DCOM in Delphi
>
>
>
>
> After using COM objects in D3 and Automation Objects in D2 for about 3
> years I can tell you quiet categorically -
>
> DONT USE DCOM !!!!! EVER !!!!!!
>
> With D3/4 you have the option of using the socket server. We
> have found
> this to be as fast (if not faster) than DCOM, it works well
> on 95 and NT,
> there is no NT security issues to worry about and it's
> simple. DCOM is a
> pain in the rear at the best of times. I've never managed to
> get server
> objects to "run as" a specific user under NT successfully, so
> you have to
> leave the server logged in as a specific user. DCOM under 95
> also requires
> that the server objects are running as they will not auto-launch.
>
> The downside of using sockets is that remote objects/servers
> have to be
> implemented as Remote Data Modules which means you are using
> Midas but you
> don't have to use TProvider - except for data access - so I
> don't know if
> licensing is required.
>
> If you want a demo some time, give me a call.
>
> Cheers
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
