For DataSnap (Midas as was), I gave up on DCom in the D5 era - it was just too much trouble to set up and dog-slow once it was.
As long as you don't understand DCOM, yes.
I changed to using Borland's ScktSrvr, which was easy to set up, fast and reliable and never looked back.
You may be surprised to know that it just acts like a DCOM proxy. DCOM is still used from the socket service to the DCOM server. Just you took DCOM security (authentication, authorization, encryption) and throw all of it away, because:
1) Your DCOM server is invoked using the socket service identity - probably the mighty (and dangerous) localsystem
2) It gets data from DCOM and transmit them in cleartext to your client (you can write a filter - but it won't implement proper security....)
3) Everybody can connect to your socket port and access the DCOM server and call its methods. DCOM instead support full Windows ACLs, down to interface methods...
Moreover, beware of 64 bit data, and other recent data types. They are unsupported.
In recent Delphi versions, there is an alternate implementation of DataSnap where the socket transport is handled by your DataSnap server, so ScktSrvr is not longer required.
And it doesn't implement any security. All of your data in cleartext. Enjoy!
Ah, and don't forget to tell everybody "Windows in not a secure operating system!"
Connect with Us