The devil is in the details for these sort of problem:
It is a complex problem because:
1. Files like pdf, doc, ... are files containing information that only the application that uses that file understands. Let's call it File Format. Unless the File Format is open (so that you know how to read the file data) then you will have to read the file through it's application. If the application (e.g. M$ Word) does not provide an API to stream a .doc file contents to the application then your other option is to open the network connection, stream the entire file and create a copy of it in the local system, then open that local file.
1.1. If for example you would like changes to the .doc file to be saved in the server, then you need to program the locking, unlocking stuff in the application that opens the file (in this case M$ Word) and the application needs to provide you with those mechanisms. If you did the local file way (as described above) then you have to take care of a problem where saving the file changes might result in a conflict. You can intergrate your network communication tool with a tool like SVN, so that SVN can pull the file for you and it will help you manage file conflict resolution.
2. If the file is not on a shared folder then you need a program running on the server to listen to client requests. With what you are planning to do, you might open a security hole through this server application.
o_O --- On Wed, 4/15/09, Duggan Kim <mdkimani@gmail.com> wrote:
|