Jump to content

FPiette

Members
  • Content Count

    1109
  • Joined

  • Last visited

  • Days Won

    15

FPiette last won the day on November 29 2023

FPiette had the most liked content!

Community Reputation

360 Excellent

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. FPiette

    ICS V9.1 Highlights

    Hard work Angus! Thanks a lot.
  2. FPiette

    Hyper-V server as host for 3 VMS

    because a usb device can only be used by one machine at a time. Virtualhere presents the device on the remote machine as though it were local. I guess multiple remote PCs can connect, but only one at a given time. The connected PC must disconnect to allow another to connect. Just guessing.
  3. FPiette

    Hyper-V server as host for 3 VMS

    Only the free version is discontinued! Here is what Jeff Woolsey, Principal PM Manager at Microsoft is saying: The only thing that was discontinued was the FREE Microsoft Hyper-V Server product because we simply don’t have the time and resources to keep producing the free version. That’s it. That’s the only thing that was deprecated. [explanation skipped] In short, Hyper-V is here for the very long run.
  4. FPiette

    TPanel + Mouse

    Select both label and panel to set MouseEnter and MouseLeave event handler or assign same event handler to both components.
  5. FPiette

    Monitor Windows application and restart if needed

    In the program to be monitored, add code to make it answer to a message (for example a TCP socket or a pipe or a Windows message). Write a second program launch the first and periodically connect to the main program and check if he gets an answer. If no answer, it kills the program et start it again. When the second program starts the first (CreateProcess), it gets an handle that can be waited to catch when the program stops normally.
  6. A good architecture, scalable architecture, is to have ONE thread for the server component for a given protocol. That thread will handle all client communications (that's OK for up to one thousand clients) and unload any processing to worker threads. You can also consider splitting the application between different processes which will handle a single protocol and possibly use IPC to make those processes talk to each other if required. Having a single process doing everything is the best way to have an unstable system almost impossible to debug.
  7. This forum is not the place to discuss any issue with Indy, nor any comparison between ICS and any other socket component. If you want to discuss about other socket components go to their support channel. You are welcome to discuss about ICS here and nothing else.
  8. If you want to use ICS in threads, a good design would be to have all socket activity executed by the thread itself. If the data to be sent comes from another thread or received data must be processed by another thread, don't share the ICS component but use standard inter-thread communication techniques to do the transfert. Note that processing by ICS is not a CPU intensive process so you won't gain much using thread. Instead it is better to keep actual data processing along with the ICS component in the thread. For example, you can use a thread in a server application to handle a single client (or a few hundreds). Use ThreadAttach and ThreadDetach to move socket handling from one thread to another thread. Writing a multi-threaded application is hugely more complex than a single-threaded application, debugging is particularly difficult. You benefit from thread when computing can be done in parallel. For file transfer operation, there is almost no processing involved so benefit is low. Don't forget that the real network throughput is frequently the limiting factor. And even if you have a fast hardware speed (1Gbps for example) doesn't means that the network card you have is able to sustain such throughput.
  9. FPiette

    [MidWare] MidWare, Delphi 12

    Midware has been developed for professional projects. It has been used for more than 10 year in a large scale application having more than 700 concurrent users on a LAN. Backend database was MS-SQL server. It has also been used it many smaller applications.
  10. FPiette

    [MidWare] MidWare, Delphi 12

    Well, Midware is much, much more than a simple stream. At the highest level, it is a TDataSet and is meant to be used as middleware in a multi-tier database application.
  11. FPiette

    [MidWare] MidWare, Delphi 12

    Thank you for trying Midware. The library doesn't support Unicode nor SSL. Unfortunately, I do not maintain this library anymore. But you are welcome to update the source code and mail it to me 😉 To make it working, you has to understand how it works... It should no be too complex to update the code for SSL.
  12. FPiette

    Return value from other application

    Do you want the exe with shared for to be launched by one application each time the application needs the form? It would be quite inefficient and you'll have to manage having several instances of the form hosting application. It is possible, but will be quite complex... Instead, you can put the form inside a DLL that each application will load. Or even simpler, just compile the form's code into the 5 applications.
  13. Just run the IDE as administrator.
  14. I don't read attached text file. You must make the effort of copying the relevant part of text in your message. I won't help you except if you follow the rules and follow what I ask you to do.
×