I would want to build an asp.net application with some kind of doucment repository in it. A user must be able to check in a document, make some changes and checkin the document.
What are your thoughts on creating the checkin-out process
Surely, the user can save the document, edit it, and upload it back. but that's not a nice way of doing this.
Ideal would be the user clicking a checkout button, then the document opens automatically, close the document and automatically the file is saved on the server. Of course this is not possible in web-world, but what are your thoughts on creating a behaviour
as close as possible to the ideal one?
stez
Member
45 Points
12 Posts
Check in-out architecture in asp.net
May 29, 2006 01:37 PM|LINK
I would want to build an asp.net application with some kind of doucment repository in it. A user must be able to check in a document, make some changes and checkin the document.
What are your thoughts on creating the checkin-out process
Surely, the user can save the document, edit it, and upload it back. but that's not a nice way of doing this.
Ideal would be the user clicking a checkout button, then the document opens automatically, close the document and automatically the file is saved on the server. Of course this is not possible in web-world, but what are your thoughts on creating a behaviour as close as possible to the ideal one?
Greetings
Tom