M
Matthias Straka
Hi!
I'm working on a website with an IHttpHandler that listens to changes ina
database and sends some text to the client. The client is always connected
to the handler, this way I can use a push method.
Every time a text is to be sent I flush the buffer. The problem is, that
there seems to be a minimum size the buffer has to have before asp.net
really flushes the buffer and sends the data.
As a workaround I insert a few 100 bytes into a <!-- --> section to get
the buffer flushed. Any flush after the first working flush works as
expected. I don't like the comment-section though. Where could the problem
be?
mat
I'm working on a website with an IHttpHandler that listens to changes ina
database and sends some text to the client. The client is always connected
to the handler, this way I can use a push method.
Every time a text is to be sent I flush the buffer. The problem is, that
there seems to be a minimum size the buffer has to have before asp.net
really flushes the buffer and sends the data.
As a workaround I insert a few 100 bytes into a <!-- --> section to get
the buffer flushed. Any flush after the first working flush works as
expected. I don't like the comment-section though. Where could the problem
be?
mat