Any gotchas moving TServerSocket app from D5 to D2007?

Question

I've done a brief Google around and found nothing but I feel I ought to ask. I'm not really expecting there to be anything, but would rather ask a question with no answers now than ask the question when it's all going wrong and discover that EVERYONE knew about a 'gotcha'...!

To make overall support/development life easier (and to bring-in madExcept etc), I'm about to take a semi-GUI app written in D5 (using NativeDB to connect to ASA6) and port it to D2007, eventually to turn it into a console app and/or a service. (The present GUI is little more than than a glorifed start/stop button and an activity log).

It's a classic TServerSocket application, listening on a specified port and running-off to do various things when clients connect. I'm not expecting any huge problems with the NativeDB side of things, but I wondered if there were any changes (bug fixes, improvements) between D5 and D2007 as far as TServerSocket goes?

We don't use blocking sockets, Indy etc - it's just TServerSocket from the scktcomp unit, straight out of the D5 Enterprise box. I'm not looking to change the code significantly unless there is something very wrong with TServerSocket under D2007. :-)

Answer 1

I think TServerSocket still ships, but isn't installed by default any more. No other gotchas that I know about.

Since these components are deprecated, you might want to look at moving to Indy, ICS or Synapse in the longer term.

Answer 2

Implementing a command line application with ICS and TServerSocket / TClientSocket might require to create an invisible window, because these components use windows messages for asynchronous operation. I have not tried it myself yet, but maybe it is documented in the ICS or sckcomp examples or sources.