Re: [twsocket] TnEmulVT: Number Rows - Important!!!!
Hi Steve, That is the correct answer, but there is a small detail that with himself not to discover. I have made a test with an application already developed and after sending code IAC, the client recive again the screen that it had previously but resize to the new size. In my case, after sending commando IAC, receipt nothing and the screen is updated Somebody can help me? Thanks in advance. Mensaje original De: [EMAIL PROTECTED] Recibido: 07/09/2005 8: 50 Para: ICS support mailingtwsocket@elists.org Asunto: Re: [twsocket] TnEmulVT: Number Rows - Important Francois Piette wrote: Yes, seem to be some communication problems. I think he is looking for the telnet escape sequence to notify the server that the terminal size has changed. Maybe it is in the telnet rfc, I'm not sure. If that's the question, I don't know the answer. I was even not aware that such esc sequence existed ! Maybe it is this one. Telnet Window Size Option ftp://ftp.rfc-editor.org/in- notes/rfc1073.txt -- Sly This message and its attachments may contain legally privileged or confidential information. This message is intended for the use of the individual or entity to which it is addressed. If you are not the addressee indicated in this message, or the employee or agent responsible for delivering the message to the intended recipient, you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e- mail. Any content of this message and its attachments, which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by the sending company or any of its related entities. No warranty is made that the e-mail or attachment(s) are free from computer virus or other defect. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www. elists.org/mailman/listinfo/twsocket Visit our website at http://www. overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] [TMimeDec] Beta version to test
Hello! And since you're too lazy to do a such simple thing, It's unfortunate your messages are so badly composed, full of capital letters which makes them hard to read, So what? My english isn't perfect, that's true. and essentially very irritating. More irritating is trying to convince me that buggy code is ok. And most irritating thing is having to remember that there's a bug in some code and you have to write special code to overcome it. I'll spend my time doing useful things, like enhancing ICS components properly, for the benefit of other. Yeah - properly, you mean, leaving old bugs as-is, just because this would cause component to behave differently? In case of problems, refer to TMimeDec (beta) sources I've really got better things to do than debug other people's source files. You've had to debug YOUR (TMimeDecEx) sources. Much easier to keep using a MineDec that works. It works - just for you. or RFC 2046. And reading an old document is hardly going to help make a Delphi program backward compatible. Got newer one? I don't think so, since there's no newer MIME specs. Just downloaded current rfc-index.txt (from http://www.rfc-editor.org), and... #v+ RFC INDEX - (CREATED ON: 09/07/2005.) This file contains citations for all RFCs in numeric order. [..] 2046 Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types. N. Freed, N. Borenstein. November 1996. (Format: TXT=105854 bytes) (Obsoletes RFC1521, RFC1522, RFC1590) (Updated by RFC2646, RFC3798) (Status: DRAFT STANDARD) [..] 2646 The Text/Plain Format Parameter. R. Gellens, Ed.. August 1999. (Format: TXT=29175 bytes) (Obsoleted by RFC3676) (Updates RFC2046) (Status: PROPOSED STANDARD) [..] 3798 Message Disposition Notification. T. Hansen, Ed., G. Vaudreuil, Ed.. May 2004. (Format: TXT=64049 bytes) (Obsoletes RFC2298) (Updates RFC3461, RFC2046) (Status: DRAFT STANDARD) #v- Certainly, reading RFC 2046 won't make Delphi program backward compatible, but at least may enlighten Delphi programmer. -- Piotr Hellrayzer Dalek [EMAIL PROTECTED] -- Seks, zdrowie, uroda, praca... http://link.interia.pl/f18b3 -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] WSocketServer stops listening
Hello Shekar, - The CPU time is that a normal load, or is this only after the server has stopped listening ? - Interesting info also is the amount / used non paged memory - and amount / used pool - do you have code in server's OnBGException ? --- Rgds, Wilfried http://www.mestdagh.biz Friday, September 9, 2005, 06:36, A.Shekar wrote: Hi, I have a program with WSocketServer. This Server just stops listening for new connections. I do a Server.Close and Server.Listen and then new connections start coming in. What could be the reason? Some info which might be useful to understand the situation. 1. 300 to 800 may be connected when the problem happens. 2. Each connection gets 2000 - 4000 bytes per second from the server. The server may receive 100 bytes from the client once in while. The application runs for about 6 hours. 3. 10-20 new connections may be requested simultaneously sometimes. 4. The CPU usage is 40-60%. (Some time back the CPU usage used to reach 100%. At that time i faced the same problem. I optimised the code and usage came below 10% and the problem vanished) 5. The software runs on W2K Server. WSocketServer.ConnectionBacklog is 200 . 6. WSocket V5.16, Single threaded application regards Shekar -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
