What's the best place to ask this question?:
I have a database that serves up the content for what will be a public website. In this site, certain users that work for our organization will be able to use a partial CMS I have built to change the contents of many of the pages.
My concern is this:
During the "Save" process, AJAX makes a round-trip to the server, and while there, nullifies the page locations of the appropriate page (so as to reuse the id), then immediately afterwards re-saves the new values to the page. Reading content from a NULL location will not cause errors or anything; it simply won't show up on the page.
I really don't mean to pick this apart too much but I am concerned that I might accidentally be setting myself up for error. My question is: Should I worry about the fraction of a second between nullifying the locations of content and when the new content gets saved?
Again, it is fault tolerant as much as possible, and I wouldn't expect to see any YSODs or anything, but what if they get no content, simply because somebody looked up the page, and it happened to be timed just right to "get in" and get the values from the database just when someone was saving edits to the given page?
Anyway, I feel a little silly as I write this question, as if I am over-complicating the issue or perhaps worrying too much, but considering the cost if I'm wrong in my approach here, I was looking for some professional advice from anyone who has programmed CMS or CMS-like websites in the past.
Things You May Want to Know:
- I am in a C#.Net Web-Pages w/ WebMatrix environment (as opposed to Web-Forms or MVC).
- The command I am using to "nullify" the page location values looks like this:
UPDATE ContentObjects SET location = NULL WHERE location = @0. Then, as soon as I programmatically can, I re-apply the values and repopulate the locations.
I was thinking super user, but then I thought about how much database information was in it, as well as an understanding of asp.net perhaps, so I'm really not sure what the best site to ask this on is.