Re: [twsocket] HTTPClient

2006-02-15 Thread Fastream Technologies
I think the timer should be reset for each data sent/got. Otherwise, for lenghtly downloads, it would simply break the it!! Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Wednesday, February 15, 2006 9:39 AM

[twsocket] Properties and event declarations

2006-02-15 Thread Dod
Hello, Is there a list of which properties and events are not inherited from the ones set after .Create and which ones must be re-set again after a socket close (for socket.connect I think it is just ip+port as they are the only ones raising an error but I am not about other

Re: [twsocket] Problem with Firewalls

2006-02-15 Thread Fastream Technologies
Hello, Have you tried the passive mode? Regards, SubZ - Original Message - From: Jean-Paul Passama [EMAIL PROTECTED] To: twsocket@elists.org Sent: Wednesday, February 15, 2006 1:30 PM Subject: [twsocket] Problem with Firewalls Hi, I have made a program which send datas (text

Re: [twsocket] Properties and event declarations

2006-02-15 Thread Francois Piette
Sorry but I don't understand the question ! Here is an answer (if it answer one of your questions): You must re-assign Addr, Port and Protocol after the socket has been closed. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Dod [EMAIL PROTECTED] To: ICS support

Re: [twsocket] Problem with Firewalls

2006-02-15 Thread Fastream Technologies
Then you have a non-transparent firewall which is indeed a proxy that requires you to enter username/password or at least provide in a format. There should be an explanation of them in the ftpcli.pas. Regards, SZ - Original Message - From: Jean-Paul Passama [EMAIL PROTECTED] To: ICS

Re: [twsocket] Properties and event declarations

2006-02-15 Thread Dod
Hello Francois, For one of the question you answered : each .Connect you must re-assign IP+Port+Proto properties. For other question I try to re-explain better. If do do this : MySocket:=TWSocket.Create(nil); MySocket.OnClientConnect:=MyOnClientConnect;

Re: [twsocket] Properties and event declarations

2006-02-15 Thread Arno Garrels
Dod wrote: Hello Francois, Yes, I mistaken : MySocket:=TWSocketServer.Create(nil); MySocket.OnClientCreate:=MyOnClientCreate; MySocket.OnClientConnect:=MyOnClientConnect; MySocket.OnDataAvailable:=MyOnDataAvailable; Doing this will not make MyOnDataAvailable work unless I also put it

Re: [twsocket] Properties and event declarations

2006-02-15 Thread Dod
Hello Arno, AG Choose more meaningfull names!! Of course I use more meaningfull names in my real code :-) That was just for sample. AG TWSocketServer also has an event OnDataAvailable, but that has _nothing to do AG with the client object. Yes, in fact this one is from TWSocket and is

Re: [twsocket] Properties and event declarations

2006-02-15 Thread Wilfried Mestdagh
Hello Dod, MySocket:=TWSocketServer.Create(nil); MySocket.OnClientCreate:=MyOnClientCreate; MySocket.OnClientConnect:=MyOnClientConnect; MySocket.OnDataAvailable:=MyOnDataAvailable; Ok what you do wrong is followin: MySocket is a server. A server never receives data, so assigning to his

Re: [twsocket] Properties and event declarations

2006-02-15 Thread Wilfried Mestdagh
Hello Dod, Of course I use more meaningfull names in my real code :-) That was just for sample. But please you confuse use choosing less meaning full names here :( As I said, this is for my FAQ and I have no real problem using TWSocketServer and TWSocket, I just try to remember the