Presuming this is a side effect of the fact that we flush-upon-completion and we don't actually
flush on each write. Usually small packets are not desireable, but this clearly calls for an
AspNet option flag to enable write-through. Looking into a patch for this, thanks for the pointer.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1985440
Originator: NO
Hi There... I to am getting the same error using version 2.2.6. Is there any indication was to when we can expect some activity on this item
thanks
Logged In: YES
user_id=1482554
Originator: NO
Well your getting it to work, I can even get it to show up or even error out.
Logged In: NO
No funciona con ajax...porfavor pronto parche.
Presuming this is a side effect of the fact that we flush-upon-completion and we don't actually
flush on each write. Usually small packets are not desireable, but this clearly calls for an
AspNet option flag to enable write-through. Looking into a patch for this, thanks for the pointer.