Matt,
Thanks for your response.
What I have is two http handlers, one that receives data, saves this data,
data must stay persistent, and another handler that receives requests for
this data, and writes a file out as the response. Both have to handle
multiple requests at the same time.
So, how would what you propose work? Would I have a string or a property in
the class that I would write data to, and it would be stored in memory? Like
I said, the data needs to persist for the lifetime of the web application
(httphandler). What happens if the server reboots?
So, back to, if the only way to do this is to write a file, which physical
location should I write the file to?
Thank a ton.
-Shefali
> Hello shefali,
>
[quoted text clipped - 32 lines]
> > Thanks.
> > -Shefali
Matt Berther - 03 Dec 2004 07:35 GMT
Hello shefali,
Fair enough... I presume that you've checked that the ASPNET account has
the appropriate NTFS permissions to actually write to that location?
--
Matt Berther
http://www.mattberther.com
> Matt,
>
[quoted text clipped - 52 lines]
>>> Thanks.
>>> -Shefali
Richard Blewett [DevelopMentor] - 03 Dec 2004 08:15 GMT
Also remember that for Win2003 by default the "Network Service" account will need write access to that location as the worker process doesn't run under the ASPNET account
Regards
Richard Blewett - DevelopMentor
http://www.dotnetconsult.co.uk/weblog
http://www.dotnetconsult.co.uk
Hello shefali,
Fair enough... I presume that you've checked that the ASPNET account has
the appropriate NTFS permissions to actually write to that location?
--
Matt Berther
http://www.mattberther.com
Matt Berther - 03 Dec 2004 15:08 GMT
Hello Richard Blewett [DevelopMentor],
Of course... Thanks for mentioning that...
--
Matt Berther
http://www.mattberther.com
> Also remember that for Win2003 by default the "Network Service"
> account will need write access to that location as the worker process
[quoted text clipped - 13 lines]
> Matt Berther
> http://www.mattberther.com
shefali - 03 Dec 2004 20:09 GMT
Matt, Richard,
Thank you for your inputs.
Like I said, I have several web apps. If I change the ASPNET account
privilege to 'administrator', that would give all the webapps on the system
full control. Instead, would it not be better, if I don't change the account
privilege for the ASPNET account (leave it to its current 'limited' setting),
and write the files 'systemroot/temp'? Reading the .net Framework developers
Guide, section 'ASP.NET Required Access Control Lists (ACLs)', it seems that
'systemroot/temp' has access type 'Read/write/delete' and this location is
used to support web services. What do you think?
Thanks again.
-Shefali
> Hello Richard Blewett [DevelopMentor],
>
[quoted text clipped - 21 lines]
> > Matt Berther
> > http://www.mattberther.com
Matt Berther - 04 Dec 2004 21:07 GMT
Hello shefali,
I wasnt suggesting you set the priviledge to 'administrator'. I suggested
that you set the permissions on the folder you want to write to to allow
the ASPNET account.
--
Matt Berther
http://www.mattberther.com
> Matt, Richard,
>
[quoted text clipped - 36 lines]
>>> Matt Berther
>>> http://www.mattberther.com
shefali - 06 Dec 2004 18:41 GMT
Thank you very much. I did just this, and 'am happy with the solution.
Thanks a ton. -Shefali
> Hello shefali,
>
[quoted text clipped - 46 lines]
> >>> Matt Berther
> >>> http://www.mattberther.com