If my inStream is huge (e.g. a huge XML file), i got my memory used up very quickly, as everything get buffered in the outStream. The outStream sends the data out, but it doesn't clear itself (as I got the sent data on the server -- I wrote a HttpModule on the server and the memory is normal there)
I also tried to use outStream.Flush() after each Write(), but didn't improve. I find that the stream may clear itself only when it's closed
I commented out outStream.Write, and the memory is ok (means that the inStream and buffer don't leak)
I also tried the asynch call, begin/endgetrequeststream, but didn't get any gd news
I'm using NetFx 1.1, I'm not sure if this is a bug or I did something wrong, pls advice, thx
Yes, the data is buffered internally. This is used because in certain situations,(eg redirect/auth) we might need to repost the dagta to a different server.
You can disable this by setting AllowWriteStreamBuffering=false on the webrequest.
-- Remove "user" from the email address to reply to the author.
This posting is provided "AS IS" with no warranties, and confers no rights
> If my inStream is huge (e.g. a huge XML file), i got my memory used up very > quickly, as everything get buffered in the outStream. The outStream sends > the data out, but it doesn't clear itself (as I got the sent data on the > server -- I wrote a HttpModule on the server and the memory is normal there)
> I also tried to use outStream.Flush() after each Write(), but didn't > improve. I find that the stream may clear itself only when it's closed
> I commented out outStream.Write, and the memory is ok (means that the > inStream and buffer don't leak)
> I also tried the asynch call, begin/endgetrequeststream, but didn't get any > gd news
> I'm using NetFx 1.1, I'm not sure if this is a bug or I did something wrong, > pls advice, thx
> Yes, the data is buffered internally. This is used because in certain > situations,(eg redirect/auth) we might need to repost the dagta to a > different server.
> You can disable this by setting AllowWriteStreamBuffering=false on the > webrequest.
> -- > Remove "user" from the email address to reply to the author.
> This posting is provided "AS IS" with no warranties, and confers no rights
> > If my inStream is huge (e.g. a huge XML file), i got my memory used up > very > > quickly, as everything get buffered in the outStream. The outStream sends > > the data out, but it doesn't clear itself (as I got the sent data on the > > server -- I wrote a HttpModule on the server and the memory is normal > there)
> > I also tried to use outStream.Flush() after each Write(), but didn't > > improve. I find that the stream may clear itself only when it's closed
> > I commented out outStream.Write, and the memory is ok (means that the > > inStream and buffer don't leak)
> > I also tried the asynch call, begin/endgetrequeststream, but didn't get > any > > gd news
> > I'm using NetFx 1.1, I'm not sure if this is a bug or I did something > wrong, > > pls advice, thx
There are settings in the machine.config file to enable windows integrated authentication. You can see the asp.net quickstarts which are part of the framework sdk.
feroze. =============== This posting is provided as is, without any warranties and confers no rights.