[twsocket] AN: New e-mail protocol (spam free and more!)

Dear friends, I have developed a complete and very improved e-mail protocol, highly immune to the SPAM, with data encryption and compression, with sender ID validation, etc. BUT not compatible with the standard email (SMTP). Let me introduce you to High Density Mail Protocol (HDMP): This very

Re: [twsocket] OFF: Mysterious dummy connections on a web-server

Fastream Technologies wrote: > Hello, > > We use two timers: one for the idle case and one for the > request/response started case. Both are required because the client > may simply power off. Winsock normally does not timeout for reasons > unknown to me... Winsock doesn't timeout because it does

Re: [twsocket] OFF: Mysterious dummy connections on a web-server

Hello, We use two timers: one for the idle case and one for the request/response started case. Both are required because the client may simply power off. Winsock normally does not timeout for reasons unknown to me... Regards, SZ On 2/6/08, S.Korotky <[EMAIL PROTECTED]> wrote: > > Hello, All! >

[twsocket] OFF: Mysterious dummy connections on a web-server

Hello, All! It's a little bit offtopic but relates to an ICS-based software, and I suppose ICS gooroos may shed some light on this. Imagine you have a public web-server (runs on Windows 2003). From time to time, some strange client software opens a connection(s) on the server but never issues a

Re: [twsocket] Access Violation at Address 00000 - When Client App terminates

Hello wayne, if your socket is attached to a thread and multithread is true then all events will fire in the same thread context. after OnSessionClosed is fired (with or without error) you should not send data after it. I think it is also a good idea to put all send operations in an exception blo

Re: [twsocket] Access Violation at Address 00000 - When Client App terminates

Thank you Wilfried, I think I have found the Problem, but still not sure what to "Check" for, I did a Stack Trace: First event is 10053 : Socket Disconnected, then because I was sending Data, this code then continues to be executed: size := Swap4(DataStream.Size);

Re: [twsocket] UDP problem

Hello Skok, Add one TWSocket for sending data and one TWSocketServer for receiving. In TWSocket do the .Send or .SendStr to 255.255.255.255 and do .Close in OnDataSent. Do .Listen for your TWSocketServer and check OnDataAvailable. That's all, I have done a tool that do same thing you want,

Re: [twsocket] Access Violation at Address 00000 - When Client App terminates

Hello wayne, Yes you probably access an object that never has created, or there is some pointer overwritten. When you have the exception view the call stack window to go to the offending code. --- Rgds, Wilfried [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html http://www.mestdagh.biz W

Re: [twsocket] UDP problem

Well, I'm trying to do server and client UDP with one component. So, if I want do receive udp packet from network, I have to do Listen on some port, and if I want to send UDP packets, I hava to do Send. But since component is already listening, I can send only with SendTo. And this sendto must

Re: [twsocket] UDP problem

Hello Skok, I don't really know what the problem is but I think you do something too complicated... A simple .Send to 255.255.255.255 is enought, then OnDataSent do a .Close why use a TTimer ? ST> I'm trying to create application that would run on multiple machines. ST> This application has to

[twsocket] Access Violation at Address 00000 - When Client App terminates

I have an Access Violation at address 0, I googled on this and found that this means a reference to a null. Basically I have implemented my Application based on "ThrdSrvV2_1" demo project, The problem happens as Follows: The Client connects to the Server, then requests data, I then Close the