Delphi：从Indy9到Indy10的迁移：使用IdCustomHTTPServer和IdHTTPServer

Question

Is there a doc on how to migrate an indy9 solution to indy10? 是否有关于如何将indy9解决方案迁移到indy10的文档？

We migrated our client pieces fine. 我们很好地迁移了客户群。

The server piece is actually a component we use (with sources) that uses: 服务器部分实际上是我们使用（带有源代码）的组件，它使用：

  IdCustomHTTPServer,
  IdHTTPServer,
  IdTCPServer,
  IdThreadMgrPool,

Any hints/docs on how indy10 has rearranged itself would be v helpful. 关于indy10如何重新安排自身的任何提示/文档都将有所帮助。

Answer 1

Is there a doc on how to migrate an indy9 solution to indy10? 是否有关于如何将indy9解决方案迁移到indy10的文档？

Not specifically, but IIRC there might be some pieces mentioned in the online documentation . 没有具体说明，但IIRC可能在联机文档中提到了一些内容。

IdCustomHTTPServer, IdCustomHTTPServer，
IdHTTPServer, IdHTTPServer，
IdTCPServer IdTCPServer

Those exist in Indy 10. 这些存在于Indy 10中。

IdThreadMgrPool, IdThreadMgrPool，

That, on the other hand, was replaced with a new TIdSchedulerOfThreadPool component. 另一方面，该组件已替换为新的TIdSchedulerOfThreadPool组件。

Any hints/docs on how indy10 has rearranged itself would be v helpful. 关于indy10如何重新安排自身的任何提示/文档都将有所帮助。

Some of the big changes are: 一些重大变化是：

Most of the TIdTCPConnection methods were moved to the TIdIOHandler class. 大多数TIdTCPConnection方法已移至TIdIOHandler类。
the TIdPeerThread class was replaced with a new TIdContext class. TIdPeerThread类被替换为新的TIdContext类。
TIdThreadMgr... components were replaced with new TIdSchedulerOfThread... components. TIdThreadMgr...组件已替换为新的TIdSchedulerOfThread...组件。

If you are having particular problems with the migration, ask questions about it. 如果您在迁移方面遇到特殊问题，请提出有关问题。