Unfortunately, I wasn't ballsy enough to speak with a rep at the company I'm quoting for desktop prices. I suspect I could have gotten a fair discount. Oh well -- it's their money, not mine, and they don't really exist anyway.
Finally, finally, finally, I'm feeling comfortable with references, due to lengthy Camel perusal.
Some back-of-the-envelope diagramming I did recently on the GUICS may have solved the conceptual problem I was having (how to handle the possibility of lots of simultaneous access attempts without confirmation of locking). Got a few options to look into:
Unless I have this thing all wrong in my head, *nix handles locking fine, la la la, but doing it on Win* requires footwork (in the form of BerkeleyDB or a sentinel file). More research required, of course.
The renewed interest in GUICS is due to my realization of reuse: If this works for my friend/client who has no deadline/timetable/hosting as-of-yet, then it might also handle the antique ceramic tile guy.
I can't believe I just typed that sentence.