Remy Lebeau (TeamB) wrote:
> "Ferenc Nemeth" <ferenc.nemeth@interticket.hu> wrote in message
> news:44a3c2b4$1@newsgroups.borland.com...
>
>> sometimes IOHandler.Connected returns with FALSE, but
>> connection is opened.
>
> That is only possible if the IOHandler was actually closed and the socket
> deallocated.
>
>> I think the problem is in the WriteBuffer.
>
> WriteBuffer() is a very core piece of Indy. If there were a problem with
> WriteBuffer(), it would effect every Indy component equally, and would have
> been noticed a long time ago. That is simply not the case here.
>
>> I know that in our developing (before a half year) there was problem
>> with writebuffer. We could change all writebuffer to writestream.
>> Since no problem.
>
> WriteStream() calls WriteBuffer(). If WriteBuffer() were failing to operate
> properly, WriteStream() would be failing as well.
Yes, that is true, but WriteBuffer does not produce this interesting
situation when using OpenWriteBuffer.. ClosewriteBuffer.
When using OpenWriteBuffer and CloseWriteBuffer then WriteBuffer does
not use LBuffer: TIdSimpleBuffer;
WriteStream does not use this type: TIdSimpleBuffer only a simple
LBuffer: TMemoryStream;
The problem is that I cannot send you a test project that works like I
said. I wrote you, send me a test project, only an exe file, I will put
it on our server. I would like only one proprty to setup: port. Send
back a file named: server.ini
Believe me, I would like if my program is working correctly, my job is
not to invent a story about errors.
best regards
Feri
>
>
> Gambit
