Re: [twsocket] Different results for one DNS Query

2006-09-15 Thread Max Terentiev
Hello, I use default settings (UDP). I will try to check it in TCP mode. --- With best regards, Max Terentiev. Business Software Products. AMS Development Team. [EMAIL PROTECTED] - Original Message - From: "Francois Piette" <[EMAIL PROTECTED]> To: "ICS support mailing" Sent: Friday,

[twsocket] TFTPServer bug on STOR command

2006-09-15 Thread Yannis Perros
Hello, I have the following problem with the TFTPServer component: I have a client which tries to send a file to the server but it cancels the connection just before the server has received the whole file and then the server issues a 10057 error. After that the server still thinks that the clien

Re: [twsocket] Different results for one DNS Query

2006-09-15 Thread Francois Piette
Are you using TCP or UDP protocol ? UDP is unreliable by design but faster. With UDP, you query or its answer may be lost. It is also possible that the target DNS server is overflowed. Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] Author of ICS (Inter

[twsocket] Different results for one DNS Query

2006-09-15 Thread Max Terentiev
Hello, I notice strange problem: I use TDNSQuery for resolving MX servers for e-mail addresses. Time to time TDNSQuery may return empty result (ResponseANCount==0) for domain. But next time for SAME domain it may return MX servers (ResponseANCount>0) Why fist time ResponseANCount is zero but

Re: [twsocket] complex problem, probably not ICS related

2006-09-15 Thread Dan
Try disabling your thread sleeping (the thread that reads from the StringList). Does your stringlist get all the the requests? i.e. is TWSocket receiving them and your code parsing and putting them in the list correctly? Dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTE

Re: [twsocket] THttpSrv supporting NTLM Beta (updated)

2006-09-15 Thread Stadin, Benjamin
You can rely on the NTLM message size. You can retrieve the message partly, write it to the context struct bytewise and when the full message is received process it and do the next step. That should be better than Receive(). SZ wrote: Because the 401 response could be sent before the POST data i

Re: [twsocket] THttpSrv supporting NTLM Beta (updated)

2006-09-15 Thread Fastream Technologies
Because the 401 response could be sent before the POST data is fully here. The same applies to all POST routines--you cannot simply rely on packet boundaries--this is TCP! Here is my approach: int ToPost = toBePostedDataLen - postedDataLen; if(ToPost > 8192) ToPost = 8192; int Len = Receive(p

Re: [twsocket] complex problem, probably not ICS related

2006-09-15 Thread Francois Piette
> Do critical sections work in the same > thread or only for different threads? Critical section work only for different threads. > The receiver puts incomming bytes into a ringbuffer with a greater size > than the buffer where TWSocket.receive puts the data in in the first > place. Then it check