D
David Arden Stevensonn
Say I have an XML file on my website that gets read alot (by a c# aspx page)
but written to occasionally (also by the same c# aspx page) . Its a simple
caching situation based on time. Example: If x minutes have elapsed return
the XML from the file and then rewrite the XML file for the next user and
reset the clock. If x minutes havent elapsed just return the XML from the
file.
Do I need to be concerned for any concurrent read/writes or other
concurrency issues? Say userA comes to the page gets a read, while a
nanosecond later userB goes to the page and triggers a read/write, or
vice-versa. Can I get a deadlock/error? If so what strategy can I use to
avoid it?
Thanks in advance
David
but written to occasionally (also by the same c# aspx page) . Its a simple
caching situation based on time. Example: If x minutes have elapsed return
the XML from the file and then rewrite the XML file for the next user and
reset the clock. If x minutes havent elapsed just return the XML from the
file.
Do I need to be concerned for any concurrent read/writes or other
concurrency issues? Say userA comes to the page gets a read, while a
nanosecond later userB goes to the page and triggers a read/write, or
vice-versa. Can I get a deadlock/error? If so what strategy can I use to
avoid it?
Thanks in advance
David