[EMAIL PROTECTED] wrote:
>
> 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 !!!!!!
good point :)
>
> 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.
You can also use CORBA, OLEnterprise or DCOM with MIDAS, and its so easy
you'll fall over yourself - if you need database connectivity. I havn't
played with it enough (yet) to know if I can call arbitary methods on
the other side, not just link to remote data modules, which is way way
way cool in its own right.
I think DCOM is an option when the client is very strapped for cash (not
a good situation in the first place) and just wants something that
works. Otherwise, go MIDAS or CORBA, depending on your requirements (and
joy! No BDE to roll out!)
Nic.
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
