baconbutty
08-11-2004, 10:07 AM
I am writing a simple ASP page, that allows several people to update a flat XML text file.
I.e. for each update, the XML file is loaded, the change applied, and the XML file is saved again, at the server.
Is there any way to set up an ASP site so that several updates can be queued, and applied when all others in the queue have been applied? Or is this a silly question.
I am not expecting a complete solution; at best just pointers to sources of information if any.
I know that I can achieve most of this by simply using the Application object to block more than one update at a time, but what I would like to achieve is that if an update is blocked, rather than the user having to resend, the update is stored by the server, and automatically retried periodically until successful or timeout.
I also know all this is not very elegant, and if I used database technology all this would be handled by the database.
I.e. for each update, the XML file is loaded, the change applied, and the XML file is saved again, at the server.
Is there any way to set up an ASP site so that several updates can be queued, and applied when all others in the queue have been applied? Or is this a silly question.
I am not expecting a complete solution; at best just pointers to sources of information if any.
I know that I can achieve most of this by simply using the Application object to block more than one update at a time, but what I would like to achieve is that if an update is blocked, rather than the user having to resend, the update is stored by the server, and automatically retried periodically until successful or timeout.
I also know all this is not very elegant, and if I used database technology all this would be handled by the database.