Re: [twsocket] OnDataAvailable

2012-01-31 Thread Brian Culverwell
I had a similar problem when converting to XE2 from Delphi7 - my TwSocket
component was designed to send a header string containing the length of the
data to follow, and then I would read that bit to get the actual data - and
then process it - but with XE2 being unicode aware - suddenly I had extra
characters in the actual transmitted message - so the counter at the
beginning of the data did not match the actual data - and therefore there
was still stuff to receive (still in the buffer) so it hung the client up.

Regards
Brian

On Wed, Feb 1, 2012 at 4:20 AM, mfisc...@bfe.tv wrote:


 Hi,
 i am using the Standard TWSocket in a Server and round about 5 Clients
 without
 LineMode. After a Client is connected to the Server, the Client starts
 immediately to send text messages. After some sort of filtering the
 messages
 are broadcasted to a subset of all connected Clients. If i start the sever
 and
 5 clients through a script on a single Windows 7 PC the following error
 occurs: After a few Bytes are exchanged one or two of the clients no longer
 call the
 callback function for OnDataAvailable. The ServerSocket and and the
 ClientSocket stay in state
 wsConnected. If i look at WireShark the Data is still transmitted from
 Server
 to Client.
 If the ClientSocket is closed, the callback for OnDataAvailable is
 triggered
 and the missing
 Bytes are received.
 Any idea in which direction my problem could be located?
 Thanks,
  M. Fischer
 --
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Help with stalling ftp client

2012-01-31 Thread Brian Culverwell
before each STOR

On Wed, Feb 1, 2012 at 6:27 AM, Info2004 info2...@asamicros.com wrote:

 On 31/01/2012 19:05, Brian Culverwell wrote:

 probably your backend ftp server has been changed to 'binary' type - and
 when receiving your request to STOR the .csv file - it is issuing a type A
 to change the mode to ASCII

 You could force the Type A before issuing your STOR.


 Brian,

 Do you mean to set ascii initially after logging on, or before each STOR
 (PutAsync) ?

 Regards,

 Andy

 --
 To unsubscribe or change your settings for TWSocket mailing list
 please goto 
 http://lists.elists.org/cgi-**bin/mailman/listinfo/twsockethttp://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


[twsocket] SITE EXEC issue

2012-01-30 Thread Brian Culverwell
Hi

I have a client ftp component written using ICS and a server component also
using ICS - everything was grand up to about 2 weeks ago, when the client
ftp was sending a SITE EXEC progname to the server - now that command
never even gets received (and therefore never executes).  This smells of
anti-virus or something but it is just the SITE EXEC that does not work -
everything else is fine.

Regards
Brian
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] SITE EXEC issue

2012-01-30 Thread Brian Culverwell
Thanks Angus and Francois - will try both your recommendations!

Brian

On Tue, Jan 31, 2012 at 6:42 AM, François Piette
francois.pie...@skynet.bewrote:

 I have a client ftp component written using ICS and a server component
 also
 using ICS - everything
 was grand up to about 2 weeks ago, when the client ftp was sending a SITE
 EXEC progname to
 the server - now that command never even gets received (and therefore
 never executes).
  This smells of anti-virus or something but it is just the SITE EXEC that
 does not work - everything else is fine.

 Use a sniffer - such as the free WireShark - see if it is a client side or
 server side issue. Using the sniffer, you'll see if the client correctly
 send the request or not. Then we may help you debug the client or server.


 --
 francois.pie...@overbyte.be
 The author of the freeware multi-tier middleware MidWare
 The author of the freeware Internet Component Suite (ICS)
 http://www.overbyte.be




 --
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be