Re: [twsocket] Cannot change port if not closed

Thanks for the information Wilfried. One thing I have realised is that my outputDebug messages are not showing (they were showing when I was using indy). You said that I should have a working message pump. Not sure what you mean here? Thanks. Sham. From: Wilfried Mestdagh [EMAIL PROTECTED]

Re: [twsocket] Cannot change port if not closed

I have tested my client with another FTP server and it seems to work. So the problem could be with my custom FTP server. In my ftp Server I do custom processing in StoreSessionClosedEvent. The only other event I have is a Authenticate event. Do I have to do anything different on the server if

Re: [twsocket] Cannot change port if not closed

Hello Sham, One thing I have realised is that my outputDebug messages are not showing (they were showing when I was using indy). The main difference is that your code is now operating in the thread context where you have created the component. How do you show the debug messages ? You said

Re: [twsocket] Cannot change port if not closed

Hello Shamresh, Do I have to do anything different on the server if I am using ftp clients in threads? Yes. By default TFTPServer will create his clients in the thread context where you have created the component, eg the main thread. Normally you dont need threads, because the component can

Re: [twsocket] Cannot change port if not closed

How are the clients related to the server? If there is no connection (the server does not wait for data from the clients) then it is as you understood, they can co-exist. If otherwise, then it is diffucult with ICS--we did it here for HTTPS Reverse Proxy, I know what I am saying... Regards,

Re: [twsocket] Cannot change port if not closed

Hi, How are the clients related to the server? Not sure what you mean here. I have a client object which has a thread associated with it. Data that needs to be ftp'd is passed as a series of objects to the client object. The client object would then do a ftp connect and then begin ftping the

Re: [twsocket] Cannot change port if not closed

Hello Sham, Yes. You can leave the programming model the same since it is mostly a good technique to make an object for the communication, containing the ftp client. And yes you can make it normal non threaded objects. As before you create as many as you want to let file transfer simulanously,

Re: [twsocket] Cannot change port if not closed

Hello Shamresh, Or can I use ICS in a blocking fashion and hence I use the same model above? Yes you can. FTP client has also sync methods. However the use of it is not encouraged. Generally it is better to do it all async as the components are designed as sutch. --- Rgds, Wilfried [TeamICS]

[twsocket] Need a fast cache class?

Hi, With help of Benjamin Stadin I've written a fast cache-like data storage based on two linked AVL-Trees for primary and secondary indexing. http://www.duodata.de/misc/delphi/AvlCache.zip Included is a small demo that demonstrates use and speed of the TCacheTree class. Beside SSL session

Re: [twsocket] Cannot change port if not closed

Hello Wilfried, I have done as you have said and it seems to work. I have removed the threads and let the onRequestDone Event handle the processing of files in each FTP Worker object. But as you also mentioned, the GUI is really sluggish and the app freezes when I try to move it. That is why

Re: [twsocket] Cannot change port if not closed

Shamresh Khan wrote: Hello Wilfried, I have done as you have said and it seems to work. I have removed the threads and let the onRequestDone Event handle the processing of files in each FTP Worker object. But as you also mentioned, the GUI is really sluggish and the app freezes when I