|
-
Sep 4th, 2008, 12:08 PM
#2
Re: [2005] .Net Remoting Design Help

My thought would be to use an xml file or some sort of disk storage so that in case the server goes down you don't loose information.
Locking issues would probably be transatory. I would put the code that opens the xml file in a procedure and have a loop in that procedure that checks to see if the file can be opened. If so, then open it. If not, then wait a few milliseconds and try again. Something along those lines.
 I always add to the reputation of those whose posts are helpful, and even occasionally to those whose posts aren't helpful but who obviously put forth a valiant effort. That is, when the system will allow it.
My war with a browser-redirect trojan
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|