Indy 10 version of IdPeerThread.stop

[rlebeau]

IdPeerThread.Stop  - I know IdPeerThread has been replaced with IdContext.

But I don't know what IdPeerThread.Stop does to know what procedure to IdContext replaced it with.

TIdPeerThread derives from TIdThread, which derives from Delphi's native TThread. TIdThread.Stop() is just a wrapper to call TThread.Terminate() or TThread.Suspend(), depending on whether the thread is being pooled or not.

While TIdThread itself still exists in Indy 10, TIdPeerThread does not. TIdTCPServer tasks have been decoupled from the threads that run them. There is no method to "stop" a TIdContext. The preferred way is to simply disconnect the client that the TIdContext is associated with, and let TIdTCPServer stop the owning thread for you.

However, if you really need to, there is a way you can access the TIdThread that is running a TIdContext, and then you can Stop() that thread. But only if TIdTCPServer.Scheduler is set to a TIdSchedulerOfThread-derived component (which it is by default, TIdSchedulerOfThreadDefault. TIdSchedulerOfThreadPool is also available):

Code:

uses
  ..., IdSchedulerOfThread;

TIdYarnOfThread(Context.Yarn).Thread.Stop();

That being said, the real question is - why are you trying to manually stop Indy's threads to begin with? You really shouldn't be doing that, even in earlier Indy versions. Can you show an example of your stopping code? There is likely a better way to handle whatever it is doing.